Restarting primary cell bandwidth part inactivity timer based on expiration of secondary cell deactivation timer

ABSTRACT

A wireless device may receive one or more messages comprising configuration parameters for a primary cell and a secondary cell. The configuration parameters may indicate a deactivation timer for the secondary cell and a bandwidth part (BWP) inactivity timer for the primary cell. The wireless device may start the deactivation timer in response to activating the secondary cell. The wireless device may start the BWP inactivity timer in response to switching an active BWP of the primary cell. The wireless device may stop the BWP inactivity timer of the primary cell based on initiating a random-access procedure for the secondary cell. In response to the deactivation timer of the secondary cell expiring during the random-access procedure, the wireless device may restart the BWP inactivity timer of the primary cell.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/086,849, filed, Nov. 2, 2020, which is a continuation of U.S. patentapplication Ser. No. 16/366,722, filed Mar. 27, 2019, which claims thebenefit of U.S. Provisional Application No. 62/650,739, filed Mar. 30,2018, and U.S. Provisional Application No. 62/650,814, filed Mar. 30,2018, all of which are hereby incorporated by reference in theirentireties.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per anaspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as peran aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stationsas per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals as per an aspect of an embodiment of the presentdisclosure.

FIG. 5B is a diagram of an example downlink channel mapping and exampledownlink physical signals as per an aspect of an embodiment of thepresent disclosure.

FIG. 6 is a diagram depicting an example transmission time or receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDMsubcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS blocktransmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam managementprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of anembodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity asper an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per anaspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of anembodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 15 is a diagram of example RRC states as per an aspect of anembodiment of the present disclosure.

FIG. 16A, FIG. 16B and FIG. 16C are examples of MAC subheaders as per anaspect of an embodiment of the present disclosure.

FIG. 17A and FIG. 17B are examples of MAC PDUs as per an aspect of anembodiment of the present disclosure.

FIG. 18A and FIG. 18B are examples of LCIDs as per an aspect of anembodiment of the present disclosure.

FIG. 19A and FIG. 19B are examples of SCell activation/deactivation MACCE as per an aspect of an embodiment of the present disclosure.

FIG. 20A and FIG. 20B are examples of downlink beam failure scenario asper an aspect of an embodiment of the present disclosure.

FIG. 21 is an example of downlink beam failure recovery requestprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 22 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure.

FIG. 23 is an example flowchart of downlink beam failure recoveryprocedure for a bandwidth part as per an aspect of an embodiment of thepresent disclosure.

FIG. 24 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure.

FIG. 25 is an example flowchart of downlink beam failure recoveryprocedure for a bandwidth part as per an aspect of an embodiment of thepresent disclosure.

FIG. 26 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure.

FIG. 27 is an example flowchart of downlink beam failure recoveryprocedure for a bandwidth part as per an aspect of an embodiment of thepresent disclosure.

FIG. 28 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure.

FIG. 29 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure.

FIG. 30 is an example flowchart of downlink beam failure recoveryprocedure for a bandwidth part as per an aspect of an embodiment of thepresent disclosure.

FIG. 31 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure.

FIG. 32 is an example flowchart of downlink beam failure recoveryprocedure for a bandwidth part as per an aspect of an embodiment of thepresent disclosure.

FIG. 33 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure.

FIG. 34 is an example flowchart of downlink beam failure recoveryprocedure for a bandwidth part as per an aspect of an embodiment of thepresent disclosure.

FIG. 35 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure.

FIG. 36 is an example flowchart of downlink beam failure recoveryprocedure for a bandwidth part as per an aspect of an embodiment of thepresent disclosure.

FIG. 37 is an example of random access procedure for a bandwidth part incarrier aggregation as per an aspect of an embodiment of the presentdisclosure.

FIG. 38 is an example flowchart of random access procedure for abandwidth part in carrier aggregation as per an aspect of an embodimentof the present disclosure.

FIG. 39 is a flow diagram of aspects of embodiments of the presentdisclosure.

FIG. 40 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 41 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 42 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 43 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 44 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 45 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 46 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 47 is a flow diagram of aspects of embodiments of the presentdisclosure.

FIG. 48 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 49 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 50 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation of beamfailure recovery procedure. Embodiments of the technology disclosedherein may be employed in the technical field of multicarriercommunication systems. More particularly, the embodiments of thetechnology disclosed herein may relate to beam failure recoveryprocedure in a multicarrier communication system.

The following Acronyms are used throughout the present disclosure:

3GPP 3rd Generation Partnership Project

-   -   5GC 5G Core Network    -   ACK Acknowledgement    -   AMF Access and Mobility Management Function    -   ARQ Automatic Repeat Request    -   AS Access Stratum    -   ASIC Application-Specific Integrated Circuit    -   BA Bandwidth Adaptation    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   BPSK Binary Phase Shift Keying    -   BWP Bandwidth Part    -   CA Carrier Aggregation    -   CC Component Carrier    -   CCCH Common Control CHannel    -   CDMA Code Division Multiple Access    -   CN Core Network    -   CP Cyclic Prefix    -   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex    -   C-RNTI Cell-Radio Network Temporary Identifier    -   CS Configured Scheduling    -   CSI Channel State Information    -   CSI-RS Channel State Information-Reference Signal    -   CQI Channel Quality Indicator    -   CSS Common Search Space    -   CU Central Unit    -   DC Dual Connectivity    -   DCCH Dedicated Control Channel    -   DCI Downlink Control Information    -   DL Downlink    -   DL-SCH Downlink Shared CHannel    -   DM-RS DeModulation Reference Signal    -   DRB Data Radio Bearer    -   DRX Discontinuous Reception    -   DTCH Dedicated Traffic Channel    -   DU Distributed Unit    -   EPC Evolved Packet Core    -   E-UTRA Evolved UMTS Terrestrial Radio Access    -   E-UTRAN Evolved-Universal Terrestrial Radio Access Network    -   FDD Frequency Division Duplex    -   FPGA Field Programmable Gate Arrays    -   F1-C F1-Control plane    -   F1-U F1-User plane    -   gNB next generation Node B    -   HARQ Hybrid Automatic Repeat reQuest    -   HDL Hardware Description Languages    -   IE Information Element    -   IP Internet Protocol    -   LCID Logical Channel Identifier    -   LTE Long Term Evolution    -   MAC Media Access Control    -   MCG Master Cell Group    -   MCS Modulation and Coding Scheme    -   MeNB Master evolved Node B    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MN Master Node    -   NACK Negative Acknowledgement    -   NAS Non-Access Stratum    -   NG CP Next Generation Control Plane    -   NGC Next Generation Core    -   NG-C NG-Control plane    -   ng-eNB next generation evolved Node B    -   NG-U NG-User plane    -   NR New Radio    -   NR MAC New Radio MAC    -   NR PDCP New Radio PDCP    -   NR PHY New Radio PHYsical    -   NR RLC New Radio RLC    -   NR RRC New Radio RRC    -   NSSAI Network Slice Selection Assistance Information    -   O&M Operation and Maintenance    -   OFDM orthogonal Frequency Division Multiplexing    -   PBCH Physical Broadcast CHannel    -   PCC Primary Component Carrier    -   PCCH Paging Control CHannel    -   PCell Primary Cell    -   PCH Paging CHannel    -   PDCCH Physical Downlink Control CHannel    -   PDCP Packet Data Convergence Protocol    -   PDSCH Physical Downlink Shared CHannel    -   PDU Protocol Data Unit    -   PHICH Physical HARQ Indicator CHannel    -   PHY PHYsical    -   PLMN Public Land Mobile Network    -   PMI Precoding Matrix Indicator    -   PRACH Physical Random Access CHannel    -   PRB Physical Resource Block    -   PSCell Primary Secondary Cell    -   PSS Primary Synchronization Signal    -   pTAG primary Timing Advance Group    -   PT-RS Phase Tracking Reference Signal    -   PUCCH Physical Uplink Control CHannel    -   PUSCH Physical Uplink Shared CHannel    -   QAM Quadrature Amplitude Modulation    -   QFI Quality of Service Indicator    -   QoS Quality of Service    -   QPSK Quadrature Phase Shift Keying    -   RA Random Access    -   RACH Random Access CHannel    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RA-RNTI Random Access-Radio Network Temporary Identifier    -   RB Resource Blocks    -   RBG Resource Block Groups    -   RI Rank indicator    -   RLC Radio Link Control    -   RRC Radio Resource Control    -   RS Reference Signal    -   RSRP Reference Signal Received Power    -   SCC Secondary Component Carrier    -   SCell Secondary Cell    -   SCG Secondary Cell Group    -   SC-FDMA Single Carrier-Frequency Division Multiple Access    -   SDAP Service Data Adaptation Protocol    -   SDU Service Data Unit    -   SeNB Secondary evolved Node B    -   SFN System Frame Number    -   S-GW Serving GateWay    -   SI System Information    -   SIB System Information Block    -   SMF Session Management Function    -   SN Secondary Node    -   SpCell Special Cell    -   SRB Signaling Radio Bearer    -   SRS Sounding Reference Signal    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   sTAG secondary Timing Advance Group    -   TA Timing Advance    -   TAG Timing Advance Group    -   TAI Tracking Area Identifier    -   TAT Time Alignment Timer    -   TB Transport Block    -   TC-RNTI Temporary Cell-Radio Network Temporary Identifier    -   TDD Time Division Duplex    -   TDMA Time Division Multiple Access    -   TTI Transmission Time Interval    -   UCI Uplink Control Information    -   UE User Equipment    -   UL Uplink    -   UL-SCH Uplink Shared CHannel    -   UPF User Plane Function    -   UPGW User Plane Gateway    -   VHDL VHSIC Hardware Description Language    -   Xn-C Xn-Control plane    -   Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CodeDivision Multiple Access (CDMA), Orthogonal Frequency Division MultipleAccess (OFDMA), Time Division Multiple Access (TDMA), Wavelettechnologies, and/or the like. Hybrid transmission mechanisms such asTDMA/CDMA, and OFDM/CDMA may also be employed. Various modulationschemes may be applied for signal transmission in the physical layer.Examples of modulation schemes include, but are not limited to: phase,amplitude, code, a combination of these, and/or the like. An exampleradio transmission method may implement Quadrature Amplitude Modulation(QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase ShiftKeying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, a RAN node may be a next generation Node B (gNB) (e.g.120A, 120B) providing New Radio (NR) user plane and control planeprotocol terminations towards a first wireless device (e.g. 110A). In anexample, a RAN node may be a next generation evolved Node B (ng-eNB)(e.g. 120C, 120D), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device (e.g. 110B). The first wireless device maycommunicate with a gNB over a Uu interface. The second wireless devicemay communicate with a ng-eNB over a Uu interface.

A gNB or an ng-eNB may host functions such as radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of UEs inRRC_INACTIVE state, distribution function for Non-Access Stratum (NAS)messages, RAN sharing, dual connectivity or tight interworking betweenNR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may beinterconnected with each other by means of Xn interface. A gNB or anng-eNB may be connected by means of NG interfaces to 5G Core Network(5GC). In an example, 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may beconnected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g. non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide functions such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer or warning message transmission.

In an example, a UPF may host functions such as anchor point forintra-/inter-Radio Access Technology (RAT) mobility (when applicable),external PDU session point of interconnect to data network, packetrouting and forwarding, packet inspection and user plane part of policyrule enforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, QoS handling for user plane, e.g. packetfiltering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplinktraffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signalingtermination, NAS signaling security, Access Stratum (AS) securitycontrol, inter Core Network (CN) node signaling for mobility between3^(rd) Generation Partnership Project (3GPP) access networks, idle modeUE reachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (subscription and policies),support of network slicing and/or Session Management Function (SMF)selection.

FIG. 2A is an example user plane protocol stack, where Service DataAdaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers andPhysical (PHY) (e.g. 215 and 225) layer may be terminated in wirelessdevice (e.g. 110) and gNB (e.g. 120) on the network side. In an example,a PHY layer provides transport services to higher layers (e.g. MAC, RRC,etc.). In an example, services and functions of a MAC sublayer maycomprise mapping between logical channels and transport channels,multiplexing/demultiplexing of MAC Service Data Units (SDUs) belongingto one or different logical channels into/from Transport Blocks (TB s)delivered to/from the PHY layer, scheduling information reporting, errorcorrection through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between UEs by means of dynamic scheduling, priority handlingbetween logical channels of one UE by means of logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. In an example, mappingrestrictions in a logical channel prioritization may control whichnumerology and/or transmission timing a logical channel may use. In anexample, an RLC sublayer may supports transparent mode (TM),unacknowledged mode (UM) and acknowledged mode (AM) transmission modes.The RLC configuration may be per logical channel with no dependency onnumerologies and/or Transmission Time Interval (TTI) durations. In anexample, Automatic Repeat Request (ARQ) may operate on any of thenumerologies and/or TTI durations the logical channel is configuredwith. In an example, services and functions of the PDCP layer for theuser plane may comprise sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g. in case of split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. In an example, services andfunctions of SDAP may comprise mapping between a QoS flow and a dataradio bearer. In an example, services and functions of SDAP may comprisemapping Quality of Service Indicator (QFI) in DL and UL packets. In anexample, a protocol entity of SDAP may be configured for an individualPDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayersand PHY (e.g. 236 and 245) layer may be terminated in wireless device(e.g. 110) and gNB (e.g. 120) on a network side and perform service andfunctions described above. In an example, RRC (e.g. 232 and 241) may beterminated in a wireless device and a gNB on a network side. In anexample, services and functions of RRC may comprise broadcast of systeminformation related to AS and NAS, paging initiated by 5GC or RAN,establishment, maintenance and release of an RRC connection between theUE and RAN, security functions including key management, establishment,configuration, maintenance and release of Signaling Radio Bearers (SRBs)and Data Radio Bearers (DRBs), mobility functions, QoS managementfunctions, UE measurement reporting and control of the reporting,detection of and recovery from radio link failure, and/or NAS messagetransfer to/from NAS from/to a UE. In an example, NAS control protocol(e.g. 231 and 251) may be terminated in the wireless device and AMF(e.g. 130) on a network side and may perform functions such asauthentication, mobility management between a UE and a AMF for 3GPPaccess and non-3GPP access, and session management between a UE and aSMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logicalchannels for a wireless device. A logical channel in the plurality oflogical channels may correspond to a radio bearer and the radio bearermay be associated with a QoS requirement. In an example, a base stationmay configure a logical channel to be mapped to one or moreTTIs/numerologies in a plurality of TTIs/numerologies. The wirelessdevice may receive a Downlink Control Information (DCI) via PhysicalDownlink Control CHannel (PDCCH) indicating an uplink grant. In anexample, the uplink grant may be for a first TTI/numerology and mayindicate uplink resources for transmission of a transport block. Thebase station may configure each logical channel in the plurality oflogical channels with one or more parameters to be used by a logicalchannel prioritization procedure at the MAC layer of the wirelessdevice. The one or more parameters may comprise priority, prioritizedbit rate, etc. A logical channel in the plurality of logical channelsmay correspond to one or more buffers comprising data associated withthe logical channel. The logical channel prioritization procedure mayallocate the uplink resources to one or more first logical channels inthe plurality of logical channels and/or one or more MAC ControlElements (CEs). The one or more first logical channels may be mapped tothe first TTI/numerology. The MAC layer at the wireless device maymultiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logicalchannel) in a MAC PDU (e.g., transport block). In an example, the MACPDU may comprise a MAC header comprising a plurality of MAC sub-headers.A MAC sub-header in the plurality of MAC sub-headers may correspond to aMAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/orone or more MAC SDUs. In an example, a MAC CE or a logical channel maybe configured with a Logical Channel IDentifier (LCID). In an example,LCID for a logical channel or a MAC CE may be fixed/pre-configured. Inan example, LCID for a logical channel or MAC CE may be configured forthe wireless device by the base station. The MAC sub-headercorresponding to a MAC CE or a MAC SDU may comprise LCID associated withthe MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/orimpact one or more processes (e.g., set values of one or more parametersof the one or more processes or start and/or stop one or more timers ofthe one or more processes) at the wireless device by employing one ormore MAC commands. The one or more MAC commands may comprise one or moreMAC control elements. In an example, the one or more processes maycomprise activation and/or deactivation of PDCP packet duplication forone or more radio bearers. The base station may transmit a MAC CEcomprising one or more fields, the values of the fields indicatingactivation and/or deactivation of PDCP duplication for the one or moreradio bearers. In an example, the one or more processes may compriseChannel State Information (CSI) transmission of on one or more cells.The base station may transmit one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells. Inan example, the one or more processes may comprise activation ordeactivation of one or more secondary cells. In an example, the basestation may transmit a MA CE indicating activation or deactivation ofone or more secondary cells. In an example, the base station maytransmit one or more MAC CEs indicating starting and/or stopping one ormore Discontinuous Reception (DRX) timers at the wireless device. In anexample, the base station may transmit one or more MAC CEs indicatingone or more timing advance values for one or more Timing Advance Groups(TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, andbase station 2, 120B) and a wireless device 110. A wireless device maybe called an UE. A base station may be called a NB, eNB, gNB, and/orng-eNB. In an example, a wireless device and/or a base station may actas a relay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g. a wireless modem, an antenna, a wiredmodem, and/or the like), at least one processor 321A, and at least oneset of program code instructions 323A stored in non-transitory memory322A and executable by the at least one processor 321A. The base station2, 120B, may comprise at least one communication interface 320B, atleast one processor 321B, and at least one set of program codeinstructions 323B stored in non-transitory memory 322B and executable bythe at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may comprise many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At Radio Resource Control (RRC)connection establishment/re-establishment/handover, one serving cell mayprovide the NAS (non-access stratum) mobility information (e.g. TrackingArea Identifier (TAI)). At RRC connection re-establishment/handover, oneserving cell may provide the security input. This cell may be referredto as the Primary Cell (PCell). In the downlink, a carrier correspondingto the PCell may be a DL Primary Component Carrier (PCC), while in theuplink, a carrier may be an UL PCC. Depending on wireless devicecapabilities, Secondary Cells (SCells) may be configured to formtogether with a PCell a set of serving cells. In a downlink, a carriercorresponding to an SCell may be a downlink secondary component carrier(DL SCC), while in an uplink, a carrier may be an uplink secondarycomponent carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to one cell. The cell ID or cell index may alsoidentify the downlink carrier or uplink carrier of the cell (dependingon the context it is used). In the disclosure, a cell ID may be equallyreferred to a carrier ID, and a cell index may be referred to a carrierindex. In an implementation, a physical cell ID or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted on a downlink carrier. A cell index may be determinedusing RRC messages. For example, when the disclosure refers to a firstphysical cell ID for a first downlink carrier, the disclosure may meanthe first physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.When the disclosure indicates that a first carrier is activated, thespecification may equally mean that a cell comprising the first carrieris activated.

A base station may transmit to a wireless device one or more messages(e.g. RRC messages) comprising a plurality of configuration parametersfor one or more cells. One or more cells may comprise at least oneprimary cell and at least one secondary cell. In an example, an RRCmessage may be broadcasted or unicasted to the wireless device. In anexample, configuration parameters may comprise common parameters anddedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). Another SI maybe transmitted via SystemInformationBlockType2. For a wireless device inan RRC_Connected state, dedicated RRC signaling may be employed for therequest and delivery of the other SI. For the wireless device in theRRC_Idle state and/or the RRC_Inactive state, the request may trigger arandom-access procedure.

A wireless device may report its radio access capability informationwhich may be static. A base station may request what capabilities for awireless device to report based on band information. When allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection witha network. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. When adding a new SCell,dedicated RRC signaling may be employed to send all required systeminformation of the SCell i.e. while in connected mode, wireless devicesmay not need to acquire broadcasted system information directly from theSCells.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells and cell groups). As part of the RRCconnection reconfiguration procedure, NAS dedicated information may betransferred from the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be to establish (or reestablish, resume) an RRC connection. an RRCconnection establishment procedure may comprise SRB1 establishment. TheRRC connection establishment procedure may be used to transfer theinitial NAS dedicated information/message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure after successful security activation. Ameasurement report message may be employed to transmit measurementresults.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g. a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 stored in non-transitory memory 315 and executable bythe at least one processor 314. The wireless device 110 may furthercomprise at least one of at least one speaker/microphone 311, at leastone keypad 312, at least one display/touchpad 313, at least one powersource 317, at least one global positioning system (GPS) chipset 318,and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding/processing, data processing, powercontrol, input/output processing, and/or any other functionality thatmay enable the wireless device 110, the base station 1 120A and/or thebase station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to thespeaker/microphone 311, the keypad 312, and/or the display/touchpad 313.The processor 314 may receive user input data from and/or provide useroutput data to the speaker/microphone 311, the keypad 312, and/or thedisplay/touchpad 313. The processor 314 in the wireless device 110 mayreceive power from the power source 317 and/or may be configured todistribute the power to the other components in the wireless device 110.The power source 317 may comprise at least one of one or more dry cellbatteries, solar cells, fuel cells, and the like. The processor 314 maybe connected to the GPS chipset 318. The GPS chipset 318 may beconfigured to provide geographic location information of the wirelessdevice 110.

The processor 314 of the wireless device 110 may further be connected toother peripherals 319, which may comprise one or more software and/orhardware modules that provide additional features and/orfunctionalities. For example, the peripherals 319 may comprise at leastone of an accelerometer, a satellite transceiver, a digital camera, auniversal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, and thelike.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110 via a wireless link 330A and/or a wireless link 330Brespectively. In an example, the communication interface 320A of thebase station 1, 120A, may communicate with the communication interface320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110 and/or thebase station 2 120B and the wireless device 110 may be configured tosend and receive transport blocks via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may employ at least one frequency carrier. Accordingto some of various aspects of embodiments, transceiver(s) may beemployed. A transceiver may be a device that comprises both atransmitter and a receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in thecommunication interface 310, 320A, 320B and the wireless link 330A, 330Bare illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6 , FIG. 7A,FIG. 7B, FIG. 8 , and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF,etc.) may comprise one or more communication interfaces, one or moreprocessors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers,switches, antennas, and/or the like) may comprise one or moreprocessors, and memory storing instructions that when executed by theone or more processors causes the node to perform certain processesand/or functions. Example embodiments may enable operation ofsingle-carrier and/or multi-carrier communications. Other exampleembodiments may comprise a non-transitory tangible computer readablemedia comprising instructions executable by one or more processors tocause operation of single-carrier and/or multi-carrier communications.Yet other example embodiments may comprise an article of manufacturethat comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a node to enable operation ofsingle-carrier and/or multi-carrier communications. The node may includeprocessors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and code stored in and/or incommunication with a memory device to implement connections, electronicdevice operations, protocol(s), protocol layers, communication drivers,device drivers, hardware operations, combinations thereof, and/or thelike.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 4A shows an example uplink transmitter forat least one physical channel. A baseband signal representing a physicaluplink shared channel may perform one or more functions. The one or morefunctions may comprise at least one of: scrambling; modulation ofscrambled bits to generate complex-valued symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; transform precoding to generate complex-valued symbols;precoding of the complex-valued symbols; mapping of precodedcomplex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 4A. These functions are illustrated as examples andit is anticipated that other mechanisms may be implemented in variousembodiments.

An example structure for modulation and up-conversion to the carrierfrequency of the complex-valued SC-FDMA or CP-OFDM baseband signal foran antenna port and/or the complex-valued Physical Random Access CHannel(PRACH) baseband signal is shown in FIG. 4B. Filtering may be employedprior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. Thebaseband signal representing a downlink physical channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

In an example, a gNB may transmit a first symbol and a second symbol onan antenna port, to a wireless device. The wireless device may infer thechannel (e.g., fading gain, multipath delay, etc.) for conveying thesecond symbol on the antenna port, from the channel for conveying thefirst symbol on the antenna port. In an example, a first antenna portand a second antenna port may be quasi co-located if one or morelarge-scale properties of the channel over which a first symbol on thefirst antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals. FIG. 5B is a diagram of an example downlinkchannel mapping and a downlink physical signals. In an example, aphysical layer may provide one or more information transfer services toa MAC and/or one or more higher layers. For example, the physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and with what characteristics data are transferred over theradio interface.

In an example embodiment, a radio network may comprise one or moredownlink and/or uplink transport channels. For example, a diagram inFIG. 5A shows example uplink transport channels comprising Uplink-SharedCHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram inFIG. 5B shows example downlink transport channels comprisingDownlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, andBroadcast CHannel (BCH) 513. A transport channel may be mapped to one ormore corresponding physical channels. For example, UL-SCH 501 may bemapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may bemapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to PhysicalDownlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to PhysicalBroadcast CHannel (PBCH) 516.

There may be one or more physical channels without a correspondingtransport channel. The one or more physical channels may be employed forUplink Control Information (UCI) 509 and/or Downlink Control Information(DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 maycarry UCI 509 from a UE to a base station. For example, PhysicalDownlink Control CHannel (PDCCH) 515 may carry DCI 517 from a basestation to a UE. NR may support UCI 509 multiplexing in PUSCH 503 whenUCI 509 and PUSCH 503 transmissions may coincide in a slot at least inpart. The UCI 509 may comprise at least one of CSI, Acknowledgement(ACK)/Negative Acknowledgement (NACK), and/or scheduling request. TheDCI 517 on PDCCH 515 may indicate at least one of following: one or moredownlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to abase station. For example, the one or more RSs may be at least one ofDemodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/orSounding RS (SRS) 508. In downlink, a base station may transmit (e.g.,unicast, multicast, and/or broadcast) one or more RSs to a UE. Forexample, the one or more RSs may be at least one of PrimarySynchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521,CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a basestation for channel estimation, for example, for coherent demodulationof one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH504). For example, a UE may transmit a base station at least one uplinkDM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least oneuplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. In an example, a base station mayconfigure a UE with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to transmit at one or more symbols of a PUSCH and/or PUCCH. Abase station may semi-statistically configure a UE with a maximum numberof front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UEmay schedule a single-symbol DM-RS and/or double symbol DM-RS based on amaximum number of front-loaded DM-RS symbols, wherein a base station mayconfigure the UE with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, e.g., at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

In an example, whether uplink PT-RS 507 is present or not may depend ona RRC configuration. For example, a presence of uplink PT-RS may beUE-specifically configured. For example, a presence and/or a pattern ofuplink PT-RS 507 in a scheduled resource may be UE-specificallyconfigured by a combination of RRC signaling and/or association with oneor more parameters employed for other purposes (e.g., Modulation andCoding Scheme (MCS)) which may be indicated by DCI. When configured, adynamic presence of uplink PT-RS 507 may be associated with one or moreDCI parameters comprising at least MCS. A radio network may supportplurality of uplink PT-RS densities defined in time/frequency domain.When present, a frequency domain density may be associated with at leastone configuration of a scheduled bandwidth. A UE may assume a sameprecoding for a DMRS port and a PT-RS port. A number of PT-RS ports maybe fewer than a number of DM-RS ports in a scheduled resource. Forexample, uplink PT-RS 507 may be confined in the scheduledtime/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channelstate estimation to support uplink channel dependent scheduling and/orlink adaptation. For example, SRS 508 transmitted by a UE may allow fora base station to estimate an uplink channel state at one or moredifferent frequencies. A base station scheduler may employ an uplinkchannel state to assign one or more resource blocks of good quality foran uplink PUSCH transmission from a UE. A base station maysemi-statistically configure a UE with one or more SRS resource sets.For an SRS resource set, a base station may configure a UE with one ormore SRS resources. An SRS resource set applicability may be configuredby a higher layer (e.g., RRC) parameter. For example, when a higherlayer parameter indicates beam management, a SRS resource in each of oneor more SRS resource sets may be transmitted at a time instant. A UE maytransmit one or more SRS resources in different SRS resource setssimultaneously. A new radio network may support aperiodic, periodicand/or semi-persistent SRS transmissions. A UE may transmit SRSresources based on one or more trigger types, wherein the one or moretrigger types may comprise higher layer signaling (e.g., RRC) and/or oneor more DCI formats (e.g., at least one DCI format may be employed for aUE to select at least one of one or more configured SRS resource sets.An SRS trigger type 0 may refer to an SRS triggered based on a higherlayer signaling. An SRS trigger type 1 may refer to an SRS triggeredbased on one or more DCI formats. In an example, when PUSCH 503 and SRS508 are transmitted in a same slot, a UE may be configured to transmitSRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS506.

In an example, a base station may semi-statistically configure a UE withone or more SRS configuration parameters indicating at least one offollowing: a SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, afrequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one ormore OFDM symbols (e.g., 4 OFDM symbols numbered in increasing orderfrom 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprisePSS/SSS 521 and PBCH 516. In an example, in the frequency domain, anSS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240contiguous subcarriers with the subcarriers numbered in increasing orderfrom 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 mayoccupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may spanacross 3 OFDM symbols and 240 subcarriers. A UE may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, e.g., with respect to Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters. A UE may not assumequasi co-location for other SS/PBCH block transmissions. A periodicityof an SS/PBCH block may be configured by a radio network (e.g., by anRRC signaling) and one or more time locations where the SS/PBCH blockmay be sent may be determined by sub-carrier spacing. In an example, aUE may assume a band-specific sub-carrier spacing for an SS/PBCH blockunless a radio network has configured a UE to assume a differentsub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522.For example, a base station may semi-statistically configure and/orreconfigure a UE with periodic transmission of downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated ad/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation ofCSI-RS resource may be triggered dynamically. In an example, CSI-RSconfiguration may comprise one or more parameters indicating at least anumber of antenna ports. For example, a base station may configure a UEwith 32 ports. A base station may semi-statistically configure a UE withone or more CSI-RS resource sets. One or more CSI-RS resources may beallocated from one or more CSI-RS resource sets to one or more UEs. Forexample, a base station may semi-statistically configure one or moreparameters indicating CSI RS resource mapping, for example, time-domainlocation of one or more CSI-RS resources, a bandwidth of a CSI-RSresource, and/or a periodicity. In an example, a UE may be configured toemploy a same OFDM symbols for downlink CSI-RS 522 and control resourceset (coreset) when the downlink CSI-RS 522 and coreset are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are the outside of PRBs configured for coreset. In anexample, a UE may be configured to employ a same OFDM symbols fordownlink CSI-RS 522 and SS/PBCH blocks when the downlink CSI-RS 522 andSS/PBCH blocks are spatially quasi co-located and resource elementsassociated with the downlink CSI-RS 522 are the outside of PRBsconfigured for SS/PBCH blocks.

In an example, a UE may transmit one or more downlink DM-RSs 523 to abase station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variableand/or configurable DM-RS patterns for data demodulation. At least onedownlink DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-statisticallyconfigure a UE with a maximum number of front-loaded DM-RS symbols forPDSCH 514. For example, a DM-RS configuration may support one or moreDM-RS ports. For example, for single user-MIMO, a DM-RS configurationmay support at least 8 orthogonal downlink DM-RS ports. For example, formultiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlinkDM-RS ports. A radio network may support, e.g., at least for CP-OFDM, acommon DM-RS structure for DL and UL, wherein a DM-RS location, DM-RSpattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may dependon a RRC configuration. For example, a presence of downlink PT-RS 524may be UE-specifically configured. For example, a presence and/or apattern of downlink PT-RS 524 in a scheduled resource may beUE-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters employed for other purposes(e.g., MCS) which may be indicated by DCI. When configured, a dynamicpresence of downlink PT-RS 524 may be associated with one or more DCIparameters comprising at least MCS. A radio network may supportplurality of PT-RS densities defined in time/frequency domain. Whenpresent, a frequency domain density may be associated with at least oneconfiguration of a scheduled bandwidth. A UE may assume a same precodingfor a DMRS port and a PT-RS port. A number of PT-RS ports may be fewerthan a number of DM-RS ports in a scheduled resource. For example,downlink PT-RS 524 may be confined in the scheduled time/frequencyduration for a UE.

FIG. 6 is a diagram depicting an example transmission time and receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers, in case ofcarrier aggregation, or ranging from 1 to 64 carriers, in case of dualconnectivity. Different radio frame structures may be supported (e.g.,for FDD and for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. In this example, radio frame duration is 10 ms. In thisexample, a 10 ms radio frame 601 may be divided into ten equally sizedsubframes 602 with 1 ms duration. Subframe(s) may comprise one or moreslots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6 , asubframe may be divided into two equally sized slots 603 with 0.5 msduration. For example, 10 subframes may be available for downlinktransmission and 10 subframes may be available for uplink transmissionsin a 10 ms interval. Uplink and downlink transmissions may be separatedin the frequency domain. Slot(s) may include a plurality of OFDM symbols604. The number of OFDM symbols 604 in a slot 605 may depend on thecyclic prefix length. For example, a slot may be 14 OFDM symbols for thesame subcarrier spacing of up to 480 kHz with normal CP. A slot may be12 OFDM symbols for the same subcarrier spacing of 60 kHz with extendedCP. A slot may contain downlink, uplink, or a downlink part and anuplink part and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as peran aspect of an embodiment of the present disclosure. In the example, agNB may communicate with a wireless device with a carrier with anexample channel bandwidth 700. Arrow(s) in the diagram may depict asubcarrier in a multicarrier OFDM system. The OFDM system may usetechnology such as OFDM technology, SC-FDMA technology, and/or the like.In an example, an arrow 701 shows a subcarrier transmitting informationsymbols. In an example, a subcarrier spacing 702, between two contiguoussubcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120KHz, 240 KHz etc. In an example, different subcarrier spacing maycorrespond to different transmission numerologies. In an example, atransmission numerology may comprise at least: a numerology index; avalue of subcarrier spacing; a type of cyclic prefix (CP). In anexample, a gNB may transmit to/receive from a UE on a number ofsubcarriers 703 in a carrier. In an example, a bandwidth occupied by anumber of subcarriers 703 (transmission bandwidth) may be smaller thanthe channel bandwidth 700 of a carrier, due to guard band 704 and 705.In an example, a guard band 704 and 705 may be used to reduceinterference to and from one or more neighbor carriers. A number ofsubcarriers (transmission bandwidth) in a carrier may depend on thechannel bandwidth of the carrier and the subcarrier spacing. Forexample, a transmission bandwidth, for a carrier with 20 MHz channelbandwidth and 15 KHz subcarrier spacing, may be in number of 1024subcarriers.

In an example, a gNB and a wireless device may communicate with multipleCCs when configured with CA. In an example, different component carriersmay have different bandwidth and/or subcarrier spacing, if CA issupported. In an example, a gNB may transmit a first type of service toa UE on a first component carrier. The gNB may transmit a second type ofservice to the UE on a second component carrier. Different type ofservices may have different service requirement (e.g., data rate,latency, reliability), which may be suitable for transmission viadifferent component carrier having different subcarrier spacing and/orbandwidth. FIG. 7B shows an example embodiment. A first componentcarrier may comprise a first number of subcarriers 706 with a firstsubcarrier spacing 709. A second component carrier may comprise a secondnumber of subcarriers 707 with a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 with athird subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. In an example, a carrier mayhave a transmission bandwidth 801. In an example, a resource grid may bein a structure of frequency domain 802 and time domain 803. In anexample, a resource grid may comprise a first number of OFDM symbols ina subframe and a second number of resource blocks, starting from acommon resource block indicated by higher-layer signaling (e.g. RRCsignaling), for a transmission numerology and a carrier. In an example,in a resource grid, a resource unit identified by a subcarrier index anda symbol index may be a resource element 805. In an example, a subframemay comprise a first number of OFDM symbols 807 depending on anumerology associated with a carrier. For example, when a subcarrierspacing of a numerology of a carrier is 15 KHz, a subframe may have 14OFDM symbols for a carrier. When a subcarrier spacing of a numerology is30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacingof a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. Inan example, a second number of resource blocks comprised in a resourcegrid of a carrier may depend on a bandwidth and a numerology of thecarrier.

As shown in FIG. 8 , a resource block 806 may comprise 12 subcarriers.In an example, multiple resource blocks may be grouped into a ResourceBlock Group (RBG) 804. In an example, a size of a RBG may depend on atleast one of: a RRC message indicating a RBG size configuration; a sizeof a carrier bandwidth; or a size of a bandwidth part of a carrier. Inan example, a carrier may comprise multiple bandwidth parts. A firstbandwidth part of a carrier may have different frequency location and/orbandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control informationcomprising a downlink or uplink resource block assignment to a wirelessdevice. A base station may transmit to or receive from, a wirelessdevice, data packets (e.g. transport blocks) scheduled and transmittedvia one or more resource blocks and one or more slots according toparameters in a downlink control information and/or RRC message(s). Inan example, a starting symbol relative to a first slot of the one ormore slots may be indicated to the wireless device. In an example, a gNBmay transmit to or receive from, a wireless device, data packetsscheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control informationcomprising a downlink assignment to a wireless device via one or morePDCCHs. The downlink assignment may comprise parameters indicating atleast modulation and coding format; resource allocation; and/or HARQinformation related to DL-SCH. In an example, a resource allocation maycomprise parameters of resource block allocation; and/or slotallocation. In an example, a gNB may dynamically allocate resources to awireless device via a Cell-Radio Network Temporary Identifier (C-RNTI)on one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible allocation when its downlink receptionis enabled. The wireless device may receive one or more downlink datapackage on one or more PDSCH scheduled by the one or more PDCCHs, whensuccessfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resourcesfor down link transmission to a wireless device. The gNB may transmitone or more RRC messages indicating a periodicity of the CS grant. ThegNB may transmit a DCI via a PDCCH addressed to a ConfiguredScheduling-RNTI (CS-RNTI) activating the CS resources. The DCI maycomprise parameters indicating that the downlink grant is a CS grant.The CS grant may be implicitly reused according to the periodicitydefined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control informationcomprising an uplink grant to a wireless device via one or more PDCCHs.The uplink grant may comprise parameters indicating at least modulationand coding format; resource allocation; and/or HARQ information relatedto UL-SCH. In an example, a resource allocation may comprise parametersof resource block allocation; and/or slot allocation. In an example, agNB may dynamically allocate resources to a wireless device via a C-RNTIon one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible resource allocation. The wirelessdevice may transmit one or more uplink data package via one or morePUSCH scheduled by the one or more PDCCHs, when successfully detectingthe one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink datatransmission to a wireless device. The gNB may transmit one or more RRCmessages indicating a periodicity of the CS grant. The gNB may transmita DCI via a PDCCH addressed to a CS-RNTI activating the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling viaPDCCH. The DCI may take a format in a plurality of formats. A DCI maycomprise downlink and/or uplink scheduling information (e.g., resourceallocation information, HARQ related parameters, MCS), request for CSI(e.g., aperiodic CQI reports), request for SRS, uplink power controlcommands for one or more cells, one or more timing information (e.g., TBtransmission/reception timing, HARQ feedback timing, etc.), etc. In anexample, a DCI may indicate an uplink grant comprising transmissionparameters for one or more transport blocks. In an example, a DCI mayindicate downlink assignment indicating parameters for receiving one ormore transport blocks. In an example, a DCI may be used by base stationto initiate a contention-free random access at the wireless device. Inan example, the base station may transmit a DCI comprising slot formatindicator (SFI) notifying a slot format. In an example, the base stationmay transmit a DCI comprising pre-emption indication notifying thePRB(s) and/or OFDM symbol(s) where a UE may assume no transmission isintended for the UE. In an example, the base station may transmit a DCIfor group power control of PUCCH or PUSCH or SRS. In an example, a DCImay correspond to an RNTI. In an example, the wireless device may obtainan RNTI in response to completing the initial access (e.g., C-RNTI). Inan example, the base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI(e.g., the wireless device may compute RA-RNTI based on resources usedfor transmission of a preamble). In an example, an RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). In an example, awireless device may monitor a group common search space which may beused by base station for transmitting DCIs that are intended for a groupof UEs. In an example, a group common DCI may correspond to an RNTIwhich is commonly configured for a group of UEs. In an example, awireless device may monitor a UE-specific search space. In an example, aUE specific DCI may correspond to an RNTI configured for the wirelessdevice.

A NR system may support a single beam operation and/or a multi-beamoperation. In a multi-beam operation, a base station may perform adownlink beam sweeping to provide coverage for common control channelsand/or downlink SS blocks, which may comprise at least a PSS, a SSS,and/or PBCH. A wireless device may measure quality of a beam pair linkusing one or more RSs. One or more SS blocks, or one or more CSI-RSresources, associated with a CSI-RS resource index (CRI), or one or moreDM-RSs of PBCH, may be used as RS for measuring quality of a beam pairlink. Quality of a beam pair link may be defined as a reference signalreceived power (RSRP) value, or a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. A RS resource and DM-RSs of a control channel may be calledQCLed when a channel characteristics from a transmission on an RS to awireless device, and that from a transmission on a control channel to awireless device, are similar or same under a configured criterion. In amulti-beam operation, a wireless device may perform an uplink beamsweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH onone or more beam pair links simultaneously depending on a capability ofa wireless device. This may increase robustness against beam pair linkblocking. A base station may transmit one or more messages to configurea wireless device to monitor PDCCH on one or more beam pair links indifferent PDCCH OFDM symbols. For example, a base station may transmithigher layer signaling (e.g. RRC signaling) or MAC CE comprisingparameters related to the Rx beam setting of a wireless device formonitoring PDCCH on one or more beam pair links. A base station maytransmit indication of spatial QCL assumption between an DL RS antennaport(s) (for example, cell-specific CSI-RS, or wireless device-specificCSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RSantenna port(s) for demodulation of DL control channel. Signaling forbeam indication for a PDCCH may be MAC CE signaling, or RRC signaling,or DCI signaling, or specification-transparent and/or implicit method,and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. The base station may transmit DCI (e.g.downlink grants) comprising information indicating the RS antennaport(s). The information may indicate RS antenna port(s) which may beQCLed with the DM-RS antenna port(s). Different set of DM-RS antennaport(s) for a DL data channel may be indicated as QCL with different setof the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. For example, in a multi-beamoperation, a base station 120 may transmit SS blocks in multiple beams,together forming a SS burst 940. One or more SS blocks may betransmitted on one beam. If multiple SS bursts 940 are transmitted withmultiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation forestimating a beam quality of a links between a wireless device and abase station. A beam may be associated with a CSI-RS. For example, awireless device may, based on a RSRP measurement on CSI-RS, report abeam index, as indicated in a CRI for downlink beam selection, andassociated with a RSRP value of a beam. A CSI-RS may be transmitted on aCSI-RS resource including at least one of one or more antenna ports, oneor more time or frequency radio resources. A CSI-RS resource may beconfigured in a cell-specific way by common RRC signaling, or in awireless device-specific way by dedicated RRC signaling, and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be transmitted periodically, or using aperiodictransmission, or using a multi-shot or semi-persistent transmission. Forexample, in a periodic transmission in FIG. 9A, a base station 120 maytransmit configured CSI-RS resources 940 periodically using a configuredperiodicity in a time domain. In an aperiodic transmission, a configuredCSI-RS resource may be transmitted in a dedicated time slot. In amulti-shot or semi-persistent transmission, a configured CSI-RS resourcemay be transmitted within a configured period. Beams used for CSI-RStransmission may have different beam width than beams used for SS-blockstransmission.

FIG. 9B is an example of a beam management procedure in an example newradio network. A base station 120 and/or a wireless device 110 mayperform a downlink L1/L2 beam management procedure. One or more of thefollowing downlink L1/L2 beam management procedures may be performedwithin one or more wireless devices 110 and one or more base stations120. In an example, a P-1 procedure 910 may be used to enable thewireless device 110 to measure one or more Transmission (Tx) beamsassociated with the base station 120 to support a selection of a firstset of Tx beams associated with the base station 120 and a first set ofRx beam(s) associated with a wireless device 110. For beamforming at abase station 120, a base station 120 may sweep a set of different TXbeams. For beamforming at a wireless device 110, a wireless device 110may sweep a set of different Rx beams. In an example, a P-2 procedure920 may be used to enable a wireless device 110 to measure one or moreTx beams associated with a base station 120 to possibly change a firstset of Tx beams associated with a base station 120. A P-2 procedure 920may be performed on a possibly smaller set of beams for beam refinementthan in the P-1 procedure 910. A P-2 procedure 920 may be a special caseof a P-1 procedure 910. In an example, a P-3 procedure 930 may be usedto enable a wireless device 110 to measure at least one Tx beamassociated with a base station 120 to change a first set of Rx beamsassociated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reportsto a base station 120. In one or more beam management reports, awireless device 110 may indicate some beam pair quality parameters,comprising at least, one or more beam identifications; RSRP; PrecodingMatrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator(RI) of a subset of configured beams. Based on one or more beammanagement reports, a base station 120 may transmit to a wireless device110 a signal indicating that one or more beam pair links are one or moreserving beams. A base station 120 may transmit PDCCH and PDSCH for awireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a BandwidthAdaptation (BA). In an example, receive and/or transmit bandwidthsconfigured by an UE employing a BA may not be large. For example, areceive and/or transmit bandwidths may not be as large as a bandwidth ofa cell. Receive and/or transmit bandwidths may be adjustable. Forexample, a UE may change receive and/or transmit bandwidths, e.g., toshrink during period of low activity to save power. For example, a UEmay change a location of receive and/or transmit bandwidths in afrequency domain, e.g. to increase scheduling flexibility. For example,a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cellmay be referred to as a Bandwidth Part (BWP). A base station mayconfigure a UE with one or more BWPs to achieve a BA. For example, abase station may indicate, to a UE, which of the one or more(configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050)with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g. RRC layer)for a cell a set of one or more BWPs (e.g., at most four BWPs) forreceptions by the UE (DL BWP set) in a DL bandwidth by at least oneparameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs)for transmissions by a UE (UL BWP set) in an UL bandwidth by at leastone parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one ormore UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA),a base station may configure a UE at least with one or more DL BWPs(e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least oneof a location and number of contiguous PRBs, a subcarrier spacing, or acyclic prefix, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a UE is configured with a secondary carrier on a primary cell, the UEmay be configured with an initial BWP for random access procedure on asecondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that acenter frequency for a DL BWP may be same as a center frequency for a ULBWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPsor one or more UL BWPs, respectively, a base statin maysemi-statistically configure a UE for a cell with one or more parametersindicating at least one of following: a subcarrier spacing; a cyclicprefix; a number of contiguous PRBs; an index in the set of one or moreDL BWPs and/or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; a DCI detection to aPDSCH reception timing; a PDSCH reception to a HARQ-ACK transmissiontiming value; a DCI detection to a PUSCH transmission timing value; anoffset of a first PRB of a DL bandwidth or an UL bandwidth,respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell,a base station may configure a UE with one or more control resource setsfor at least one type of common search space and/or one UE-specificsearch space. For example, a base station may not configure a UE withouta common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station mayconfigure a UE with one or more resource sets for one or more PUCCHtransmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicatorfield value may indicate an active DL BWP, from a configured DL BWP set,for one or more DL receptions. If a DCI comprises a BWP indicator field,a BWP indicator field value may indicate an active UL BWP, from aconfigured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statisticallyconfigure a UE with a default DL BWP among configured DL BWPs. If a UEis not provided a default DL BWP, a default BWP may be an initial activeDL BWP.

In an example, a base station may configure a UE with a timer value fora PCell. For example, a UE may start a timer, referred to as BWPinactivity timer, when a UE detects a DCI indicating an active DL BWP,other than a default DL BWP, for a paired spectrum operation or when aUE detects a DCI indicating an active DL BWP or UL BWP, other than adefault DL BWP or UL BWP, for an unpaired spectrum operation. The UE mayincrement the timer by an interval of a first value (e.g., the firstvalue may be 1 millisecond or 0.5 milliseconds) if the UE does notdetect a DCI during the interval for a paired spectrum operation or foran unpaired spectrum operation. In an example, the timer may expire whenthe timer is equal to the timer value. A UE may switch to the default DLBWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of BWP inactivity timer(for example, the second BWP may be a default BWP). For example, FIG. 10is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2(1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a defaultBWP. BWP1 (1010) may be an initial active BWP. In an example, a UE mayswitch an active BWP from BWP1 1010 to BWP2 1020 in response to anexpiry of BWP inactivity timer. For example, a UE may switch an activeBWP from BWP2 1020 to BWP3 1030 in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in responseto receiving a DCI indicating an active BWP and/or in response to anexpiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a defaultDL BWP among configured DL BWPs and a timer value, UE procedures on asecondary cell may be same as on a primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DLBWP and a first active UL BWP on a secondary cell or carrier, a UE mayemploy an indicated DL BWP and an indicated UL BWP on a secondary cellas a respective first active DL BWP and first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity(e.g. dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A is an example diagram of a protocol structure of awireless device 110 (e.g. UE) with CA and/or multi connectivity as peran aspect of an embodiment. FIG. 11B is an example diagram of a protocolstructure of multiple base stations with CA and/or multi connectivity asper an aspect of an embodiment. The multiple base stations may comprisea master node, MN 1130 (e.g. a master node, a master base station, amaster gNB, a master eNB, and/or the like) and a secondary node, SN 1150(e.g. a secondary node, a secondary base station, a secondary gNB, asecondary eNB, and/or the like). A master node 1130 and a secondary node1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception/transmissionfunctions in an RRC connected state, may be configured to utilize radioresources provided by multiple schedulers of a multiple base stations.Multiple base stations may be inter-connected via a non-ideal or idealbackhaul (e.g. Xn interface, X2 interface, and/or the like). A basestation involved in multi connectivity for a certain wireless device mayperform at least one of two different roles: a base station may eitheract as a master base station or as a secondary base station. In multiconnectivity, a wireless device may be connected to one master basestation and one or more secondary base stations. In an example, a masterbase station (e.g. the MN 1130) may provide a master cell group (MCG)comprising a primary cell and/or one or more secondary cells for awireless device (e.g. the wireless device 110). A secondary base station(e.g. the SN 1150) may provide a secondary cell group (SCG) comprising aprimary secondary cell (PSCell) and/or one or more secondary cells for awireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a beareremploys may depend on how a bearer is setup. In an example, threedifferent type of bearer setup options may be supported: an MCG bearer,an SCG bearer, and/or a split bearer. A wireless device mayreceive/transmit packets of an MCG bearer via one or more cells of theMCG, and/or may receive/transmits packets of an SCG bearer via one ormore cells of an SCG. Multi-connectivity may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not beconfigured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmitand/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer viaan SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one ofa master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and oneof a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119);and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), aPDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and aMAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondarybase station (e.g. SN 1150) may transmit/receive: packets of an MCGbearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and amaster node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via amaster or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), asecondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and asecondary node MAC layer (e.g. SN MAC 1148); packets of a split bearervia a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), amaster or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SNRLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g.MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities: one MAC entity (e.g. MN MAC 1118) for a master base station,and other MAC entities (e.g. SN MAC 1119) for a secondary base station.In multi-connectivity, a configured set of serving cells for a wirelessdevice may comprise two subsets: an MCG comprising serving cells of amaster base station, and SCGs comprising serving cells of a secondarybase station. For an SCG, one or more of following configurations may beapplied: at least one cell of an SCG has a configured UL CC and at leastone cell of a SCG, named as primary secondary cell (PSCell, PCell ofSCG, or sometimes called PCell), is configured with PUCCH resources;when an SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or a number of NR RLC retransmissions hasbeen reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, forsplit bearer, a DL data transfer over a master base station may bemaintained; an NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer; PCell and/or PSCell may not be de-activated; PSCellmay be changed with a SCG change procedure (e.g. with security keychange and a RACH procedure); and/or a bearer type change between asplit bearer and a SCG bearer or simultaneous configuration of a SCG anda split bearer may or may not supported.

With respect to interaction between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be applied: a master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice; a master base station may (e.g. based on received measurementreports, traffic conditions, and/or bearer types) may decide to requesta secondary base station to provide additional resources (e.g. servingcells) for a wireless device; upon receiving a request from a masterbase station, a secondary base station may create/modify a containerthat may result in configuration of additional serving cells for awireless device (or decide that the secondary base station has noresource available to do so); for a UE capability coordination, a masterbase station may provide (a part of) an AS configuration and UEcapabilities to a secondary base station; a master base station and asecondary base station may exchange information about a UE configurationby employing of RRC containers (inter-node messages) carried via Xnmessages; a secondary base station may initiate a reconfiguration of thesecondary base station existing serving cells (e.g. PUCCH towards thesecondary base station); a secondary base station may decide which cellis a PSCell within a SCG; a master base station may or may not changecontent of RRC configurations provided by a secondary base station; incase of a SCG addition and/or a SCG SCell addition, a master basestation may provide recent (or the latest) measurement results for SCGcell(s); a master base station and secondary base stations may receiveinformation of SFN and/or subframe offset of each other from OAM and/orvia an Xn interface, (e.g. for a purpose of DRX alignment and/oridentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signaling may be used for sending requiredsystem information of a cell as for CA, except for a SFN acquired from aMIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival during RRC_CONNECTED when UL synchronization status isnon-synchronized, transition from RRC_Inactive, and/or request for othersystem information. For example, a PDCCH order, a MAC entity, and/or abeam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least oneof a contention based random access procedure and a contention freerandom access procedure. For example, a contention based random accessprocedure may comprise, one or more Msg1 1220 transmissions, one or moreMsg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. For example, a contention free random accessprocedure may comprise one or more Msg1 1220 transmissions and one ormore Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, orbroadcast), to a UE, a RACH configuration 1210 via one or more beams.The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: available set of PRACH resourcesfor a transmission of a random access preamble, initial preamble power(e.g., random access preamble initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., random access preamble powerramping step), random access preamble index, a maximum number ofpreamble transmission, preamble group A and group B, a threshold (e.g.,message size) to determine the groups of random access preambles, a setof one or more random access preambles for system information requestand corresponding PRACH resource(s), if any, a set of one or more randomaccess preambles for beam failure recovery request and correspondingPRACH resource(s), if any, a time window to monitor RA response(s), atime window to monitor response(s) on beam failure recovery request,and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of arandom access preamble. For a contention based random access procedure,a UE may select a SS block with a RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a UE may select one or morerandom access preambles from a group A or a group B depending on apotential Msg3 1240 size. If a random access preambles group B does notexist, a UE may select the one or more random access preambles from agroup A. A UE may select a random access preamble index randomly (e.g.with equal probability or a normal distribution) from one or more randomaccess preambles associated with a selected group. If a base stationsemi-statistically configures a UE with an association between randomaccess preambles and SS blocks, the UE may select a random accesspreamble index randomly with equal probability from one or more randomaccess preambles associated with a selected SS block and a selectedgroup.

For example, a UE may initiate a contention free random access procedurebased on a beam failure indication from a lower layer. For example, abase station may semi-statistically configure a UE with one or morecontention free PRACH resources for beam failure recovery requestassociated with at least one of SS blocks and/or CSI-RSs. If at leastone of SS blocks with a RSRP above a first RSRP threshold amongstassociated SS blocks or at least one of CSI-RSs with a RSRP above asecond RSRP threshold amongst associated CSI-RSs is available, a UE mayselect a random access preamble index corresponding to a selected SSblock or CSI-RS from a set of one or more random access preambles forbeam failure recovery request.

For example, a UE may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. If a base station does not configure a UE with at least onecontention free PRACH resource associated with SS blocks or CSI-RS, theUE may select a random access preamble index. If a base stationconfigures a UE with one or more contention free PRACH resourcesassociated with SS blocks and at least one SS block with a RSRP above afirst RSRP threshold amongst associated SS blocks is available, the UEmay select the at least one SS block and select a random access preamblecorresponding to the at least one SS block. If a base station configuresa UE with one or more contention free PRACH resources associated withCSI-RSs and at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available, the UE may selectthe at least one CSI-RS and select a random access preamblecorresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting theselected random access preamble. For example, if a UE selects an SSblock and is configured with an association between one or more PRACHoccasions and one or more SS blocks, the UE may determine an PRACHoccasion from one or more PRACH occasions corresponding to a selected SSblock. For example, if a UE selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs,the UE may determine a PRACH occasion from one or more PRACH occasionscorresponding to a selected CSI-RS. A UE may transmit, to a basestation, a selected random access preamble via a selected PRACHoccasions. A UE may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. A UE may determine a RA-RNTIassociated with a selected PRACH occasions in which a selected randomaccess preamble is transmitted. For example, a UE may not determine aRA-RNTI for a beam failure recovery request. A UE may determine anRA-RNTI at least based on an index of a first OFDM symbol and an indexof a first slot of a selected PRACH occasions, and/or an uplink carrierindex for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random accessresponse, Msg2 1230. A UE may start a time window (e.g., ra-ResponseWindow) to monitor a random access response. For beam failure recoveryrequest, a base station may configure a UE with a different time window(e.g., bfr-Response Window) to monitor response on beam failure recoveryrequest. For example, a UE may start a time window (e.g., ra-ResponseWindow or bfr-Response Window) at a start of a first PDCCH occasionafter a fixed duration of one or more symbols from an end of a preambletransmission. If a UE transmits multiple preambles, the UE may start atime window at a start of a first PDCCH occasion after a fixed durationof one or more symbols from an end of a first preamble transmission. AUE may monitor a PDCCH of a cell for at least one random access responseidentified by a RA-RNTI or for at least one response to beam failurerecovery request identified by a C-RNTI while a timer for a time windowis running.

In an example, a UE may consider a reception of random access responsesuccessful if at least one random access response comprises a randomaccess preamble identifier corresponding to a random access preambletransmitted by the UE. A UE may consider the contention free randomaccess procedure successfully completed if a reception of random accessresponse is successful. If a contention free random access procedure istriggered for a beam failure recovery request, a UE may consider acontention free random access procedure successfully complete if a PDCCHtransmission is addressed to a C-RNTI. In an example, if at least onerandom access response comprises a random access preamble identifier, aUE may consider the random access procedure successfully completed andmay indicate a reception of an acknowledgement for a system informationrequest to upper layers. If a UE has signaled multiple preambletransmissions, the UE may stop transmitting remaining preambles (if any)in response to a successful reception of a corresponding random accessresponse.

In an example, a UE may perform one or more Msg 3 1240 transmissions inresponse to a successful reception of random access response (e.g., fora contention based random access procedure). A UE may adjust an uplinktransmission timing based on a timing advanced command indicated by arandom access response and may transmit one or more transport blocksbased on an uplink grant indicated by a random access response.Subcarrier spacing for PUSCH transmission for Msg3 1240 may be providedby at least one higher layer (e.g. RRC) parameter. A UE may transmit arandom access preamble via PRACH and Msg3 1240 via PUSCH on a same cell.A base station may indicate an UL BWP for a PUSCH transmission of Msg31240 via system information block. A UE may employ HARQ for aretransmission of Msg3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting asame preamble to a base station and receive, from the base station, asame random access response comprising an identity (e.g., TC-RNTI).Contention resolution 1250 may ensure that a UE does not incorrectly usean identity of another UE. For example, contention resolution 1250 maybe based on C-RNTI on PDCCH or a UE contention resolution identity onDL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UEmay perform contention resolution 1250 based on a reception of a PDCCHtransmission that is addressed to the C-RNTI. In response to detectionof a C-RNTI on a PDCCH, a UE may consider contention resolution 1250successful and may consider a random access procedure successfullycompleted. If a UE has no valid C-RNTI, a contention resolution may beaddressed by employing a TC-RNTI. For example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises a UE contention resolutionidentity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UEmay consider the contention resolution 1250 successful and may considerthe random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of anembodiment. In an example, a wireless device may be configured tooperate in a multi-connectivity mode. A wireless device in RRC_CONNECTEDwith multiple RX/TX may be configured to utilize radio resourcesprovided by multiple schedulers located in a plurality of base stations.The plurality of base stations may be connected via a non-ideal or idealbackhaul over the Xn interface. In an example, a base station in aplurality of base stations may act as a master base station or as asecondary base station. A wireless device may be connected to one masterbase station and one or more secondary base stations. A wireless devicemay be configured with multiple MAC entities, e.g. one MAC entity formaster base station, and one or more other MAC entities for secondarybase station(s). In an example, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 illustrates an examplestructure for MAC entities when MCG and SCG are configured for awireless device.

In an example, at least one cell in a SCG may have a configured UL CC,wherein a cell of at least one cell may be called PSCell or PCell ofSCG, or sometimes may be simply called PCell. A PSCell may be configuredwith PUCCH resources. In an example, when a SCG is configured, there maybe at least one SCG bearer or one split bearer. In an example, upondetection of a physical layer problem or a random access problem on aPSCell, or upon reaching a number of RLC retransmissions associated withthe SCG, or upon detection of an access problem on a PSCell during a SCGaddition or a SCG change: an RRC connection re-establishment proceduremay not be triggered, UL transmissions towards cells of an SCG may bestopped, a master base station may be informed by a UE of a SCG failuretype and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transferand radio resource allocation to upper layers (e.g. 1310 or 1320). A MACsublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360).A MAC sublayer may provide data transfer services on logical channels.To accommodate different kinds of data transfer services, multiple typesof logical channels may be defined. A logical channel may supporttransfer of a particular type of information. A logical channel type maybe defined by what type of information (e.g., control or data) istransferred. For example, BCCH, PCCH, CCCH and DCCH may be controlchannels and DTCH may be a traffic channel. In an example, a first MACentity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCHand MAC control elements. In an example, a second MAC entity (e.g. 1320)may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,signaling of scheduling request or measurements (e.g. CQI). In anexample, in dual connectivity, two MAC entities may be configured for awireless device: one for MCG and one for SCG. A MAC entity of wirelessdevice may handle a plurality of transport channels. In an example, afirst MAC entity may handle first transport channels comprising a PCCHof MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one ormore first UL-SCHs of MCG and one or more first RACHs of MCG. In anexample, a second MAC entity may handle second transport channelscomprising a second BCH of SCG, one or more second DL-SCHs of SCG, oneor more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells,there may be multiple DL-SCHs and there may be multiple UL-SCHs as wellas multiple RACHs per MAC entity. In an example, there may be one DL-SCHand UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero orone UL-SCH and zero or one RACH for an SCell. A DL-SCH may supportreceptions using different numerologies and/or TTI duration within a MACentity. A UL-SCH may also support transmissions using differentnumerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and maycontrol these functions with a control (e.g. 1355 or 1365) element.Functions performed by a MAC entity may comprise mapping between logicalchannels and transport channels (e.g., in uplink or downlink),multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TB) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g. 1352 or 1362) of MAC SDUs to one or different logical channelsfrom transport blocks (TB) delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink or downlink(e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or1361). A MAC entity may handle a random access process (e.g. 1354 or1364).

FIG. 14 is an example diagram of a RAN architecture comprising one ormore base stations. In an example, a protocol stack (e.g. RRC, SDAP,PDCP, RLC, MAC, and PHY) may be supported at a node. A base station(e.g. gNB 120A or 120B) may comprise a base station central unit (CU)(e.g. gNB-CU 1420A or 1420B) and at least one base station distributedunit (DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g. CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. In an example, an Xn interface may be configuredbetween base station CUs.

In an example, a base station CU may comprise an RRC function, an SDAPlayer, and a PDCP layer, and base station DUs may comprise an RLC layer,a MAC layer, and a PHY layer. In an example, various functional splitoptions between a base station CU and base station DUs may be possibleby locating different combinations of upper protocol layers (RANfunctions) in a base station CU and different combinations of lowerprotocol layers (RAN functions) in base station DUs. A functional splitmay support flexibility to move protocol layers between a base stationCU and base station DUs depending on service requirements and/or networkenvironments.

In an example, functional split options may be configured per basestation, per base station CU, per base station DU, per UE, per bearer,per slice, or with other granularities. In per base station CU split, abase station CU may have a fixed split option, and base station DUs maybe configured to match a split option of a base station CU. In per basestation DU split, a base station DU may be configured with a differentsplit option, and a base station CU may provide different split optionsfor different base station DUs. In per UE split, a base station (basestation CU and at least one base station DUs) may provide differentsplit options for different wireless devices. In per bearer split,different split options may be utilized for different bearers. In perslice splice, different split options may be applied for differentslices.

FIG. 15 is an example diagram showing RRC state transitions of awireless device. In an example, a wireless device may be in at least oneRRC state among an RRC connected state (e.g. RRC_Connected 1530,RRC_Connected), an RRC idle state (e.g. RRC Idle 1510, RRC_Idle), and/oran RRC inactive state (e.g. RRC_Inactive 1520, RRC_Inactive). In anexample, in an RRC connected state, a wireless device may have at leastone RRC connection with at least one base station (e.g. gNB and/or eNB),which may have a UE context of the wireless device. A UE context (e.g. awireless device context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an example, in an RRC idle state, a wireless device may nothave an RRC connection with a base station, and a UE context of awireless device may not be stored in a base station. In an example, inan RRC inactive state, a wireless device may not have an RRC connectionwith a base station. A UE context of a wireless device may be stored ina base station, which may be called as an anchor base station (e.g. lastserving base station).

In an example, a wireless device may transition a UE RRC state betweenan RRC idle state and an RRC connected state in both ways (e.g.connection release 1540 or connection establishment 1550; or connectionreestablishment) and/or between an RRC inactive state and an RRCconnected state in both ways (e.g. connection inactivation 1570 orconnection resume 1580). In an example, a wireless device may transitionits RRC state from an RRC inactive state to an RRC idle state (e.g.connection release 1560).

In an example, an anchor base station may be a base station that maykeep a UE context (a wireless device context) of a wireless device atleast during a time period that a wireless device stays in a RANnotification area (RNA) of an anchor base station, and/or that awireless device stays in an RRC inactive state. In an example, an anchorbase station may be a base station that a wireless device in an RRCinactive state was lastly connected to in a latest RRC connected stateor that a wireless device lastly performed an RNA update procedure in.In an example, an RNA may comprise one or more cells operated by one ormore base stations. In an example, a base station may belong to one ormore RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from anRRC connected state to an RRC inactive state in a base station. Awireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RANpaging message) to base stations of an RNA to reach to a wireless devicein an RRC inactive state, and/or the base stations receiving the messagefrom the anchor base station may broadcast and/or multicast anothermessage (e.g. paging message) to wireless devices in their coveragearea, cell coverage area, and/or beam coverage area associated with theRNA through an air interface.

In an example, when a wireless device in an RRC inactive state movesinto a new RNA, the wireless device may perform an RNA update (RNAU)procedure, which may comprise a random access procedure by the wirelessdevice and/or a UE context retrieve procedure. A UE context retrieve maycomprise: receiving, by a base station from a wireless device, a randomaccess preamble; and fetching, by a base station, a UE context of thewireless device from an old anchor base station. Fetching may comprise:sending a retrieve UE context request message comprising a resumeidentifier to the old anchor base station and receiving a retrieve UEcontext response message comprising the UE context of the wirelessdevice from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state mayselect a cell to camp on based on at least a on measurement results forone or more cells, a cell where a wireless device may monitor an RNApaging message and/or a core network paging message from a base station.In an example, a wireless device in an RRC inactive state may select acell to perform a random access procedure to resume an RRC connectionand/or to transmit one or more packets to a base station (e.g. to anetwork). In an example, if a cell selected belongs to a different RNAfrom an RNA for a wireless device in an RRC inactive state, the wirelessdevice may initiate a random access procedure to perform an RNA updateprocedure. In an example, if a wireless device in an RRC inactive statehas one or more packets, in a buffer, to transmit to a network, thewireless device may initiate a random access procedure to transmit oneor more packets to a base station of a cell that the wireless deviceselects. A random access procedure may be performed with two messages(e.g. 2 stage random access) and/or four messages (e.g. 4 stage randomaccess) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplinkpackets from a wireless device in an RRC inactive state may fetch a UEcontext of a wireless device by transmitting a retrieve UE contextrequest message for the wireless device to an anchor base station of thewireless device based on at least one of an AS context identifier, anRNA identifier, a base station identifier, a resume identifier, and/or acell identifier received from the wireless device. In response tofetching a UE context, a base station may transmit a path switch requestfor a wireless device to a core network entity (e.g. AMF, MME, and/orthe like). A core network entity may update a downlink tunnel endpointidentifier for one or more bearers established for the wireless devicebetween a user plane core network entity (e.g. UPF, S-GW, and/or thelike) and a RAN node (e.g. the base station), e.g. changing a downlinktunnel endpoint identifier from an address of the anchor base station toan address of the base station.

A gNB may communicate with a wireless device via a wireless networkemploying one or more new radio technologies. The one or more radiotechnologies may comprise at least one of: multiple technologies relatedto physical layer; multiple technologies related to medium accesscontrol layer; and/or multiple technologies related to radio resourcecontrol layer. Example embodiments of enhancing the one or more radiotechnologies may improve performance of a wireless network. Exampleembodiments may increase the system throughput, or data rate oftransmission. Example embodiments may reduce battery consumption of awireless device. Example embodiments may improve latency of datatransmission between a gNB and a wireless device. Example embodimentsmay improve network coverage of a wireless network. Example embodimentsmay improve transmission efficiency of a wireless network.

Example MAC PDU structure.

A gNB may transmit one or more MAC PDU to a wireless device. In anexample, a MAC PDU may be a bit string that is byte aligned (e.g.,multiple of eight bits) in length. In an example, bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table, and more generally, the bitstring may be read from the left to right and then in the reading orderof the lines. In an example, the bit order of a parameter field within aMAC PDU is represented with the first and most significant bit in theleftmost bit and the last and least significant bit in the rightmostbit.

In an example, a MAC SDU may be a bit string that is byte aligned (e.g.,multiple of eight bits) in length. In an example, a MAC SDU may beincluded into a MAC PDU from the first bit onward.

In an example, a MAC CE may be a bit string that is byte aligned (e.g.,multiple of eight bits) in length.

In an example, a MAC subheader may be a bit string that is byte aligned(e.g., multiple of eight bits) in length. In an example, a MAC subheadermay be placed immediately in front of the corresponding MAC SDU, or MACCE, or padding.

In an example, a MAC entity may ignore a value of reserved bits in a DLMAC PDU.

In an example, a MAC PDU may comprise one or more MAC subPDUs. a MACsubPDU of the one or more MAC subPDUs may comprise at least one of: aMAC subheader only (including padding); a MAC subhearder and a MAC SDU;a MAC subheader and a MAC CE; and/or a MAC subheader and padding. In anexample, the MAC SDU may be of variable size. In an example, a MACsubhearder may correspond to a MAC SDU, or a MAC CE, or padding.

In an example, a MAC subheader may comprise: an R field with one bit; aF field with one bit in length; a LCID field with multiple bits inlength; a L field with multiple bits in length, when the MAC subheadercorresponds to a MAC SDU, or a variable-sized MAC CE, or padding.

FIG. 16A shows example of a MAC subheader with an eight-bit L field. Inthe example, the LCID field may have six bits in length, and the L fieldmay have eight bits in length. FIG. 16B shows example of a MAC subheaderwith a sixteen-bit L field. In the example, the LCID field may have sixbits in length, and the L field may have sixteen bits in length.

In an example, a MAC subheader may comprise: a R field with two bits inlength; and a LCID field with multiple bits in length, when the MACsubheader corresponds to a fixed sized MAC CE, or padding. FIG. 16Cshows example of the MAC subheader. In the example, the LCID field mayhave six bits in length, and the R field may have two bits in length.

FIG. 17A shows example of a DL MAC PDU. In the example, multiple MAC CEsmay be placed together. A MAC subPDU comprising MAC CE may be placedbefore any MAC subPDU comprising a MAC SDU, or a MAC subPDU comprisingpadding.

FIG. 17B shows example of a UL MAC PDU. In the example, multiple MAC CEsmay be placed together. A MAC subPDU comprising MAC CE may be placedafter all MAC subPDU comprising a MAC SDU. The MAC subPDU may be placedbefore a MAC subPDU comprising padding.

In an example, a MAC entity of a gNB may transmit to a MAC entity of awireless device one or more MAC CEs. FIG. 18A shows example of multipleLCIDs associated with the one or more MAC CEs. In the example, the oneor more MAC CEs may comprise at least one of: a UE contention resolutionidentity MAC CE; a timing advance command MAC CE; a DRX command MAC CE;a Long DRX command MAC CE; a SCell activation/deactivation MAC CE (1Octet); a SCell activation/deactivation MAC CE (4 Octet); and/or aduplication activation/deactivation MAC CE. In an example, a MAC CE mayhave a LCID in the corresponding MAC subheader. Different MAC CE mayhave different LCID in the corresponding MAC subheader. For example, theLCID with 111011 in a MAC subheader may indicate a MAC CE associatedwith the MAC subheader is a long DRX command MAC CE.

In an example, the MAC entity of the wireless device may transmit to theMAC entity of the gNB one or more MAC CEs. FIG. 18B shows example of theone or more MAC CEs. The one or more MAC CEs may comprise at least oneof: a short buffer status report (BSR) MAC CE; a long BSR MAC CE; aC-RNTI MAC CE; a configured grant confirmation MAC CE; a single entryPHR MAC CE; a multiple entry PHR MAC CE; a short truncated BSR; and/or along truncated BSR. In an example, a MAC CE may have a LCID in thecorresponding MAC subheader. Different MAC CE may have different LCID inthe corresponding MAC subheader. For example, the LCID with 111011 in aMAC subheader may indicate a MAC CE associated with the MAC subheader isa short-truncated command MAC CE.

Example of Carrier Aggregation

In a carrier aggregation (CA), two or more component carriers (CCs) maybe aggregated. A wireless device may simultaneously receive or transmiton one or more CCs depending on capabilities of the wireless device. Inan example, the CA may be supported for contiguous CCs. In an example,the CA may be supported for non-contiguous CCs.

When configured with a CA, a wireless device may have one RRC connectionwith a network. During an RRC connectionestablishment/re-establishment/handover, a cell providing a NAS mobilityinformation may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may be referredto as a primary cell (PCell). In an example, a gNB may transmit, to awireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells),depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell for an efficientbattery consumption. When a wireless device is configured with one ormore SCells, a gNB may activate or deactivate at least one of the one ormore SCells. Upon configuration of an SCell, the SCell may bedeactivated.

In an example, a wireless device may activate/deactivate an SCell inresponse to receiving an SCell Activation/Deactivation MAC CE.

In an example, a base station may transmit, to a wireless device, one ormore messages comprising an sCellDeactivationTimer timer. In an example,a wireless device may deactivate an SCell in response to an expiry ofthe sCellDeactivationTimer timer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising SRS transmissions on the SCell, CQI/PMI/RI/CRIreporting for the SCell on a PCell, PDCCH monitoring on the SCell, PDCCHmonitoring for the SCell on the PCell, and/or PUCCH transmissions on theSCell.

In an example, in response to the activating the SCell, the wirelessdevice may start or restart an sCellDeactivationTimer timer associatedwith the SCell. The wireless device may start the sCellDeactivationTimertimer in the slot when the SCell Activation/Deactivation MAC CE has beenreceived. In an example, in response to the activating the SCell, thewireless device may (re-)initialize one or more suspended configureduplink grants of a configured grant Type 1 associated with the SCellaccording to a stored configuration. In an example, in response to theactivating the SCell, the wireless device may trigger PHR.

In an example, when a wireless device receives an SCellActivation/Deactivation MAC CE deactivating an activated SCell, thewireless device may deactivate the activated SCell.

In an example, when an sCellDeactivationTimer timer associated with anactivated SCell expires, the wireless device may deactivate theactivated SCell. In response to the deactivating the activated SCell,the wireless device may stop the sCellDeactivationTimer timer associatedwith the activated SCell. In an example, in response to the deactivatingthe activated SCell, the wireless device may clear one or moreconfigured downlink assignments and/or one or more configured uplinkgrant Type 2 associated with the activated SCell. In an example, inresponse to the deactivating the activated SCell, the wireless devicemay further suspend one or more configured uplink grant Type 1associated with the activated SCell. The wireless device may flush HARQbuffers associated with the activated SCell.

In an example, when an SCell is deactivated, a wireless device may notperform operations comprising transmitting SRS on the SCell, reportingCQI/PMI/RI/CRI for the SCell on a PCell, transmitting on UL-SCH on theSCell, transmitting on RACH on the SCell, monitoring at least one firstPDCCH on the SCell, monitoring at least one second PDCCH for the SCellon the PCell, transmitting a PUCCH on the SCell.

In an example, when at least one first PDCCH on an activated SCellindicates an uplink grant or a downlink assignment, a wireless devicemay restart an sCellDeactivationTimer timer associated with theactivated SCell. In an example, when at least one second PDCCH on aserving cell (e.g. a PCell or an SCell configured with PUCCH, i.e. PUCCHSCell) scheduling the activated SCell indicates an uplink grant or adownlink assignment for the activated SCell, a wireless device mayrestart an sCellDeactivationTimer timer associated with the activatedSCell.

In an example, when an SCell is deactivated, if there is an ongoingrandom access procedure on the SCell, a wireless device may abort theongoing random access procedure on the SCell.

Example of SCell Activation/Deactivation MAC-CE

FIG. 19A shows an example of an SCell Activation/Deactivation MAC CE ofone octet. A first MAC PDU subheader with a first LCID may identify theSCell Activation/Deactivation MAC CE of one octet. FIG. 18A shows anexample of the first LCID. The SCell Activation/Deactivation MAC CE ofone octet may have a fixed size. The SCell Activation/Deactivation MACCE of one octet may comprise a single octet. The single octet maycomprise a first number of C-fields (e.g. seven) and a second number ofR-fields (e.g. one).

FIG. 19B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID may identifythe SCell Activation/Deactivation MAC CE of four octets. FIG. 18B showsan example of the second LCID. The SCell Activation/Deactivation MAC CEof four octets may have a fixed size. The SCell Activation/DeactivationMAC CE of four octets may comprise four octets. The four octets maycomprise a third number of C-fields (e.g. 31) and a fourth number ofR-fields (e.g. 1).

In FIG. 19A and/or FIG. 19B, a C_i field may indicate anactivation/deactivation status of an SCell with an SCell index i. In anexample, when the C_i field is set to one, an SCell with an SCell indexi may be activated. In an example, when the C_i field is set to zero, anSCell with an SCell index i may be deactivated. In FIG. 19A and FIG.19B, an R field may indicate a reserved bit. The R field may be set tozero.

Example Bandwidth Parts (BWPs)

A base station (gNB) may configure a wireless device (UE) with uplink(UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidthadaptation (BA) on a PCell. If carrier aggregation is configured, thegNB may configure the UE with at least DL BWP(s) (i.e. there may be noUL BWPS in the UL) to enable BA on an SCell. For the PCell, a firstinitial BWP may be a first BWP used for initial access. For the SCell, asecond initial BWP is a second BWP configured for the UE to firstoperate at the SCell when the SCell is activated.

In paired spectrum (e.g. FDD), a first DL and a first UL can switch BWPindependently. In unpaired spectrum (e.g. TDD), a second DL and a secondUL switch BWP simultaneously. Switching between configured BWPs mayhappen by means of a DCI or an inactivity timer. When the inactivitytimer is configured for a serving cell, an expiry of the inactivitytimer associated to that cell may switch an active BWP to a default BWP.The default BWP may be configured by the network.

In an example, for FDD systems, when configured with BA, one UL BWP foreach uplink carrier and one DL BWP may be active at a time in an activeserving cell. In an example, for TDD systems, one DL/UL BWP pair may beactive at a time in an active serving cell. Operating on the one UL BWPand the one DL BWP (or the one DL/UL pair) may enable reasonable UEbattery consumption. BWPs other than the one UL BWP and the one DL BWPthat the UE may be configured with may be deactivated. On deactivatedBWPs, the UE may not monitor PDCCH, may not transmit on PUCCH, PRACH andUL-SCH.

In an example, a Serving Cell may be configured with at most a firstnumber (e.g., four) BWPs. In an example, for an activated Serving Cell,there may be one active BWP at any point in time.

In an example, a BWP switching for a Serving Cell may be used toactivate an inactive BWP and deactivate an active BWP at a time. In anexample, the BWP switching may be controlled by a PDCCH indicating adownlink assignment or an uplink grant. In an example, the BWP switchingmay be controlled by an inactivity timer (e.g.bandwidthpartInactivityTimer). In an example, the BWP switching may becontrolled by a MAC entity in response to initiating a Random Accessprocedure. Upon addition of SpCell or activation of an SCell, one BWPmay be initially active without receiving a PDCCH indicating a downlinkassignment or an uplink grant. The active BWP for a Serving Cell may beindicated by RRC and/or PDCCH. In an example, for unpaired spectrum, aDL BWP may be paired with a UL BWP, and BWP switching may be common forboth UL and DL.

In an example, a MAC entity may apply normal operations on an active BWPfor an activated Serving Cell configured with a BWP including:transmitting on UL-SCH; transmitting on RACH; monitoring a PDCCH;transmitting PUCCH; receiving DL-SCH; (re-) initializing any suspendedconfigured uplink grants of configured grant Type 1 according to astored configuration, if any, and to start in a symbol based on someprocedure.

In an example, on an inactive BWP for each activated Serving Cellconfigured with a BWP, a MAC entity may not transmit on UL-SCH; may nottransmit on RACH; may not monitor a PDCCH; may not transmit PUCCH; maynot transmit SRS, may not receive DL-SCH; may clear any configureddownlink assignment and configured uplink grant of configured grant Type2; may suspend any configured uplink grant of configured Type 1.

In an example, upon initiation of a Random Access procedure, if PRACHresources are configured for an active UL BWP, a MAC entity may performthe Random Access procedure on an active DL BWP and the active UL BWP.In an example, upon initiation of a Random Access procedure, if PRACHresources are not configured for an active UL BWP, a MAC entity mayswitch to an initial DL BWP and an initial UL BWP. In response to theswitching, the MAC entity may perform the Random Access procedure on theinitial DL BWP and the initial UL BWP.

In an example, if a MAC entity receives a PDCCH for a BWP switching of aserving cell while a Random Access procedure associated with thisserving cell is not ongoing, a UE may perform the BWP switching to a BWPindicated by the PDCCH.

In an example, if a MAC entity receives a PDCCH for a BWP switchingwhile a Random Access procedure is ongoing in the MAC entity, it may beup to UE implementation whether to switch BWP or ignore the PDCCH forthe BWP switching. In an example, if the MAC entity decides to performthe BWP switching, the MAC entity may stop the ongoing Random Accessprocedure and initiate a second Random Access procedure on a newactivated BWP. In an example, if the MAC decides to ignore the PDCCH forthe BWP switching, the MAC entity may continue with the ongoing RandomAccess procedure on the active BWP.

In an example, if a MAC entity receives a PDCCH for a BWP switchingaddressed to a C-RNTI for a successful completion of a Random Accessprocedure, a UE may perform the BWP switching to a BWP indicated by thePDCCH.

In an example, if a BWP-InactivityTimer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not the initial BWP: if a PDCCHaddressed to C-RNTI or CS-RNTI indicating downlink assignment or uplinkgrant is received on the active BWP: if there is not an ongoing randomaccess procedure associated with the activated Serving Cell, the MACentity may start or restart the BWP-InactivityTimer associated with theactive DL BWP.

In an example, if a BWP-InactivityTimer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not the initial BWP: if aMAC-PDU is transmitted in a configured uplink grant or received in aconfigured downlink assignment; if there is not an ongoing random accessprocedure associated with the activated Serving Cell, the MAC entity maystart or restart the BWP-InactivityTimer associated with the active DLBWP.

In an example, if a BWP-InactivityTimer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not the initial BWP: if a PDCCHaddressed to C-RNTI or CS-RNTI indicating downlink assignment or uplinkgrant is received on the active BWP; or if a MAC-PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment:if an ongoing random access procedure associated with the activatedServing Cell is successfully completed in response to receiving thePDCCH addressed to a C-RNTI, the MAC entity may start or restart theBWP-InactivityTimer associated with the active DL BWP.

In an example, if a BWP-InactivityTimer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not the initial BWP: if a PDCCHfor a BWP switching is received on the active DL BWP, a MAC entity maystart or restart the BWP-InactivityTimer associated with the active DLBWP in response to switching the active BWP.

In an example, if BWP-InactivityTimer is configured, for an activatedServing Cell, if the Default-DL-BWP is configured, and the active DL BWPis not the BWP indicated by the Default-DL-BWP; or if the Default-DL-BWPis not configured, and the active DL BWP is not the initial BWP: ifRandom Access procedure is initiated, the MAC entity may stop theBWP-InactivityTimer associated with the active DL BWP of the activatedServing Cell. If the activated Serving Cell is an SCell (other than aPSCell), the MAC entity may stop a second BWP-InactivityTimer associatedwith a second active DL BWP of an SpCell.

In an example, if BWP-InactivityTimer is configured, for an activatedServing Cell, if the Default-DL-BWP is configured, and the active DL BWPis not the BWP indicated by the Default-DL-BWP; or if the Default-DL-BWPis not configured, and the active DL BWP is not the initial BWP: ifBWP-InactivityTimer associated with the active DL BWP expires: if theDefault-DL-BWP is configured, the MAC entity may perform BWP switchingto a BWP indicated by the Default-DL-BWP. Otherwise, the MAC entity mayperform BWP switching to the initial DL BWP.

In an example, a UE may be configured for operation in bandwidth parts(BWPs) of a serving cell. In an example, the UE may be configured byhigher layers for the serving cell a set of (e.g., at most four)bandwidth parts (BWPs) for receptions by the UE (e.g., DL BWP set) in aDL bandwidth by parameter DL-BWP. In an example, the UE may beconfigured with a set of (e.g., at most four) BWPs for transmissions bythe UE (e.g., UL BWP set) in an UL bandwidth by parameter UL-BWP for theserving cell.

In an example, an initial active DL BWP may be defined, for example, bya location and number of contiguous PRBs, a subcarrier spacing, and acyclic prefix, for the control resource set for Type0-PDCCH commonsearch space. In an example, for operation on a primary cell, a UE maybe provided by higher layer with a parameter initial-UL-BWP, an initialactive UL BWP for a random access procedure.

In an example, if a UE has a dedicated BWP configuration, the UE may beprovided by higher layer parameter Active-BWP-DL-Pcell a first active DLBWP for receptions. If a UE has a dedicated BWP configuration, the UEmay be provided by higher layer parameter Active-BWP-UL-Pcell a firstactive UL BWP for transmissions on a primary cell.

In an example, for a DL BWP or an UL BWP in a set of DL BWPs or UL BWPs,respectively, the UE may be configured with the following parameters forthe serving cell: a subcarrier spacing provided by higher layerparameter DL-BWP-mu or UL-BWP-mu; a cyclic prefix provided by higherlayer parameter DL-BWP-CP or UL-BWP-CP; a PRB offset with respect to thePRB determined by higher layer parameters offset-pointA-low-scs andref-scs and a number of contiguous PRBs provided by higher layerparameter DL-BWP-BW or UL-BWP-BW; an index in the set of DL BWPs or ULBWPs by respective higher layer parameters DL-BWP-index or UL-BWP-index;a DCI format 1_0 or DCI format 1_1 detection to a PDSCH reception timingvalues by higher layer parameter DL-data-time-domain; a PDSCH receptionto a HARQ-ACK transmission timing values by higher layer parameterDL-data-DL-acknowledgement; and a DCI 0_0 or DCI 0_1 detection to aPUSCH transmission timing values by higher layer parameterUL-data-time-domain;

In an example, for an unpaired spectrum operation, a DL BWP from a setof configured DL BWPs with index provided by higher layer parameterDL-BWP-index may be paired with an UL BWP from a set of configured ULBWPs with index provided by higher layer parameter UL-BWP-index when theDL BWP index and the UL BWP index are equal. For unpaired spectrumoperation, a UE may not be expected to receive a configuration where thecenter frequency for a DL BWP is different than the center frequency foran UL BWP when the DL-BWP-index of the DL BWP is equal to theUL-BWP-index of the UL BWP.

In an example, for a DL BWP in a set of DL BWPs on the primary cell, aUE may be configured control resource sets for every type of commonsearch space and for UE-specific search space. In an example, the UE maynot be expected to be configured without a common search space on thePCell, or on the PSCell, in the active DL BWP. In an example, for an ULBWP in a set of UL BWPs, the UE may be configured resource sets forPUCCH transmissions. In an example, a UE may receive PDCCH and PDSCH ina DL BWP according to a configured subcarrier spacing and CP length forthe DL BWP. A UE may transmit PUCCH and PUSCH in an UL BWP according toa configured subcarrier spacing and CP length for the UL BWP.

In an example, if a bandwidth part indicator field is configured in DCIformat 1_1, the bandwidth part indicator field value may indicate theactive DL BWP, from the configured DL BWP set, for DL receptions. In anexample, if a bandwidth part indicator field is configured in DCI format0_1, the bandwidth part indicator field value may indicate the active ULBWP, from the configured UL BWP set, for UL transmissions. In anexample, for the primary cell, a UE may be provided by higher layerparameter Default-DL-BWP, a default DL BWP among the configured DL BWPs.In an example, if a UE is not provided a default DL BWP by higher layerparameter Default-DL-BWP, the default BWP may be the initial active DLBWP.

In an example, a UE may be expected to detect a DCI format 0_1indicating active UL BWP change, or a DCI format 1_1 indicating activeDL BWP change, only if a corresponding PDCCH is received within first 3symbols of a slot.

In an example, for a primary cell, a UE may be provided by a higherlayer parameter Default-DL-BWP a default DL BWP among the configured DLBWPs. If a UE is not provided a default DL BWP by the higher layerparameter Default-DL-BWP, the default DL BWP is the initial active DLBWP.

In an example, a UE may be provided by higher layer parameterBWP-InactivityTimer, a timer value for the primary cell. If configured,the UE may increment the timer, if running, every interval of 1millisecond for frequency range 1 or every 0.5 milliseconds forfrequency range 2 if the UE may not detect a DCI format 1_1 for pairedspectrum operation or if the UE may not detect a DCI format 1_1 or DCIformat 0_1 for unpaired spectrum operation during the interval.

In an example, if a UE is configured for a secondary cell with higherlayer parameter Default-DL-BWP indicating a default DL BWP among theconfigured DL BWPs and the UE is configured with higher layer parameterBWP-InactivityTimer indicating a timer value, the UE procedures on thesecondary cell may be same as on the primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a UE is configured by higher layer parameterActive-BWP-DL-SCell a first active DL BWP and by higher layer parameterActive-BWP-UL-SCell a first active UL BWP on a secondary cell orcarrier, the UE may use the indicated DL BWP and the indicated UL BWP onthe secondary cell as the respective first active DL BWP and firstactive UL BWP on the secondary cell or carrier.

In an example, for paired spectrum operation, a UE may not be expectedto transmit HARQ-ACK on a PUCCH resource indicated by a DCI format 1_0or a DCI format 1_1 if the UE changes its active UL BWP on a PCellbetween a time of a detection of the DCI format 1_0 or the DCI format1_1 and a time of a corresponding HARQ-ACK transmission on the PUCCH.

In an example, a UE may not be expected to monitor PDCCH when the UEperforms RRM measurements over a bandwidth that is not within the activeDL BWP for the UE.

Example Downlink Control Information (DCI)

In an example, a gNB may transmit a DCI via a PDCCH for at least one of:scheduling assignment/grant; slot format notification; pre-emptionindication; and/or power-control commends. More specifically, the DCImay comprise at least one of: identifier of a DCI format; downlinkscheduling assignment(s); uplink scheduling grant(s); slot formatindicator; pre-emption indication; power-control for PUCCH/PUSCH; and/orpower-control for SRS.

In an example, a downlink scheduling assignment DCI may compriseparameters indicating at least one of: identifier of a DCI format; PDSCHresource indication; transport format; HARQ information; controlinformation related to multiple antenna schemes; and/or a command forpower control of the PUCCH.

In an example, an uplink scheduling grant DCI may comprise parametersindicating at least one of: identifier of a DCI format; PUSCH resourceindication; transport format; HARQ related information; and/or a powercontrol command of the PUSCH.

In an example, different types of control information may correspond todifferent DCI message sizes. For example, supporting multiple beamsand/or spatial multiplexing in the spatial domain and noncontiguousallocation of RBs in the frequency domain may require a largerscheduling message, in comparison with an uplink grant allowing forfrequency-contiguous allocation. DCI may be categorized into differentDCI formats, where a format corresponds to a certain message size and/orusage.

In an example, a wireless device may monitor one or more PDCCH fordetecting one or more DCI with one or more DCI format, in common searchspace or wireless device-specific search space. In an example, awireless device may monitor PDCCH with a limited set of DCI format, tosave power consumption. The more DCI format to be detected, the morepower be consumed at the wireless device.

In an example, the information in the DCI formats for downlinkscheduling may comprise at least one of: identifier of a DCI format;carrier indicator; RB allocation; time resource allocation; bandwidthpart indicator; HARQ process number; one or more MCS; one or more NDI;one or more RV; MIMO related information; Downlink assignment index(DAI); TPC for PUCCH; SRS request; and padding if necessary. In anexample, the MIMO related information may comprise at least one of: PMI;precoding information; transport block swap flag; power offset betweenPDSCH and reference signal; reference-signal scrambling sequence; numberof layers; and/or antenna ports for the transmission; and/orTransmission Configuration Indication (TCI).

In an example, the information in the DCI formats used for uplinkscheduling may comprise at least one of: an identifier of a DCI format;carrier indicator; bandwidth part indication; resource allocation type;RB allocation; time resource allocation; MCS; NDI; Phase rotation of theuplink DMRS; precoding information; CSI request; SRS request; Uplinkindex/DAI; TPC for PUSCH; and/or padding if necessary.

In an example, a gNB may perform CRC scrambling for a DCI, beforetransmitting the DCI via a PDCCH. The gNB may perform CRC scrambling bybinarily adding multiple bits of at least one wireless device identifier(e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SPCSI C-RNTI, or TPC-SRS-RNTI) on the CRC bits of the DCI. The wirelessdevice may check the CRC bits of the DCI, when detecting the DCI. Thewireless device may receive the DCI when the CRC is scrambled by asequence of bits that is the same as the at least one wireless deviceidentifier.

In an example, in order to support wide bandwidth operation, a gNB maytransmit one or more PDCCH in different control resource sets(coresets). A gNB may transmit one or more RRC message comprisingconfiguration parameters of one or more coresets. A coreset may compriseat least one of: a first OFDM symbol; a number of consecutive OFDMsymbols; a set of resource blocks; a CCE-to-REG mapping. In an example,a gNB may transmit a PDCCH in a dedicated coreset for particularpurpose, for example, for beam failure recovery confirmation.

In an example, a wireless device may monitor PDCCH for detecting DCI inone or more configured coresets, to reduce the power consumption.

Example of a BFRQ procedure.

A gNB and/or a wireless device may have multiple antennas, to support atransmission with high data rate in a NR system. When configured withmultiple antennas, a wireless device may perform one or more beammanagement procedures, as shown in FIG. 9B.

A wireless device may perform a downlink beam management based on one ormore CSI-RSs, and/or one or more SS block. In a beam managementprocedure, a wireless device may measure a channel quality of a beampair link. The beam pair link may comprise a transmitting beam from agNB and a receiving beam at the wireless device. When configured withmultiple beams associated with multiple CSI-RSs or SS blocks, a wirelessdevice may measure the multiple beam pair links between the gNB and thewireless device.

In an example, a wireless device may transmit one or more beammanagement reports to a gNB. In a beam management report, the wirelessdevice may indicate one or more beam pair quality parameters, comprisingat least, one or more beam identifications; RSRP; PMI/CQI/RI of at leasta subset of configured multiple beams.

In an example, a gNB and/or a wireless device may perform a downlinkbeam management procedure on one or multiple Transmission and ReceivingPoint (TRPs), as shown in FIG. 9B. Based on a wireless device's beammanagement report, a gNB may transmit to the wireless device a signalindicating that a new beam pair link is a serving beam. The gNB maytransmit PDCCH and PDSCH to the wireless device using the serving beam.

In an example, a wireless device or a gNB may trigger a beam failurerecovery mechanism. A wireless device may trigger a beam failurerecovery request (BFRQ) procedure, e.g., when at least a beam failureoccurs. In an example, a beam failure may occur when quality of beampair link(s) of at least one PDCCH falls below a threshold. Thethreshold may be a RSRP value (e.g., −140 dbm, −110 dbm) or a SINR value(e.g., −3 dB, −1 dB), which may be configured in a RRC message.

FIG. 20A shows example of a first beam failure scenario. In the example,a gNB may transmit a PDCCH from a transmission (Tx) beam to a receiving(Rx) beam of a wireless device from a TRP. When the PDCCH on the beampair link (between the Tx beam of the gNB and the Rx beam of thewireless device) have a lower-than-threshold RSRP/SINR value due to thebeam pair link being blocked (e.g., by a moving car or a building), thegNB and the wireless device may start a beam failure recovery procedureon the TRP.

FIG. 20B shows example of a second beam failure scenario. In theexample, the gNB may transmit a PDCCH from a beam to a wireless devicefrom a first TRP. When the PDCCH on the beam is blocked, the gNB and thewireless device may start a beam failure recovery procedure on a newbeam on a second TRP.

In an example, a wireless device may measure quality of beam pair linkusing one or more RSs. The one or more RSs may be one or more SS blocks,or one or more CSI-RS resources. A CSI-RS resource may be identified bya CSI-RS resource index (CRI). In an example, quality of beam pair linkmay be defined as a RSRP value, or a reference signal received quality(e.g. RSRQ) value, and/or a CSI (e.g., SINR) value measured on RSresources. In an example, a gNB may indicate whether an RS resource,used for measuring beam pair link quality, is QCLed (Quasi-Co-Located)with DM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH maybe called QCLed when the channel characteristics from a transmission onan RS to a wireless device, and that from a transmission on a PDCCH tothe wireless device, are similar or same under a configured criterion.In an example, The RS resource and the DM-RSs of the PDCCH may be calledQCLed when doppler shift and/or doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are same.

In an example, a wireless device may monitor PDCCH on M beam (e.g. 2, 4,8) pair links simultaneously, where M≥1 and the value of M may depend atleast on capability of the wireless device. In an example, monitoring aPDCCH may comprise detecting a DCI via the PDCCH transmitted on commonsearch spaces and/or wireless device specific search spaces. In anexample, monitoring multiple beam pair links may increase robustnessagainst beam pair link blocking. In an example, a gNB may transmit oneor more messages comprising parameters indicating a wireless device tomonitor PDCCH on different beam pair link(s) in different OFDM symbols.

In an example, a gNB may transmit one or more RRC messages or MAC CEscomprising parameters indicating Rx beam setting of a wireless devicefor monitoring PDCCH on multiple beam pair links. A gNB may transmit anindication of spatial QCL between an DL RS antenna port(s) and DL RSantenna port(s) for demodulation of DL control channel. In an example,the indication may be a parameter in a MAC CE, or a RRC message, or aDCI, and/or combination of these signaling.

In an example, for reception of data packet on a PDSCH, a gNB mayindicate spatial QCL parameters between DL RS antenna port(s) and DM-RSantenna port(s) of DL data channel. A gNB may transmit DCI comprisingparameters indicating the RS antenna port(s) QCLed with DM-RS antennaport(s).

In an example, when a gNB transmits a signal indicating QCL parametersbetween CSI-RS and DM-RS for PDCCH, a wireless device may measure a beampair link quality based on CSI-RSs QCLed with DM-RS for PDCCH. In anexample, when multiple contiguous beam failures occur, the wirelessdevice may start a BFRQ procedure.

In an example, a wireless device transmits a BFRQ signal on an uplinkphysical channel to a gNB when starting a BFRQ procedure. The gNB maytransmit a DCI via a PDCCH in a coreset in response to receiving theBFRQ signal on the uplink physical channel. The wireless may considerthe BFRQ procedure successfully completed when receiving the DCI via thePDCCH in the coreset.

In an example, a gNB may transmit one or more messages comprisingconfiguration parameters of an uplink physical channel or signal fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH(BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (BFR-PUCCH); and/or a contention-basedPRACH resource (CF-PRACH). Combinations of these candidatesignal/channels may be configured by the gNB. In an example, whenconfigured with multiple resources for a BFRQ signal, a wireless devicemay autonomously select a first resource for transmitting the BFRQsignal. In an example, when configured with a BFR-PRACH resource, aBFR-PUCCH resource, and a CF-PRACH resource, the wireless device mayselect the BFR-PRACH resource for transmitting the BFRQ signal. In anexample, when configured with a BFR-PRACH resource, a BFR-PUCCHresource, and a CF-PRACH resource, the gNB may transmit a message to thewireless device indicating a resource for transmitting the BFRQ signal.

In an example, a gNB may transmit a response to a wireless device afterreceiving one or more BFRQ signals. The response may comprise the CRIassociated with the candidate beam the wireless device indicates in theone or multiple BFRQ signals.

In an NR system, when configured with multiple beams, a gNB and/or awireless device may perform one or more beam management procedure. Forexample, the wireless device may perform a BFRQ procedure, if one ormore beam pair links between the gNB and the wireless device fail.

FIG. 21 shows example of the BFR procedure. A wireless device mayreceive one or more RRC messages comprising BFR parameters. The wirelessdevice may detect at least one beam failure according to at least one ofBFR parameters. The wireless device may start a first timer ifconfigured in response to detecting the at least one beam failure. Thewireless device may select a selected beam in response to detecting theat least one beam failure. The selected beam may be a beam with goodchannel quality (e.g., RSRP, SINR, or BLER) from a set of candidatebeams. The candidate beams may be identified by a set of referencesignals (e.g., SSBs, or CSI-RSs). The wireless device may transmit atleast a first BFR signal to a gNB in response to the selecting theselected beam. The at least first BFR signal may be associated with theselected beam. The wireless device may transmit the at least first BFRsignal with a transmission beam corresponding to a receiving beamassociated with the selected beam. The at least BFR signal may be apreamble transmitted on a PRACH resource, or a SR signal transmitted ona PUCCH resource, or a beam failure recovery signal transmitted on aPUCCH resource, or a beam report transmitted on a PUCCH/PUSCH resource.The wireless device may start a response window in response totransmitting the at least first BFR signal. In an example, the responsewindow may be a timer with a value configured by the gNB. When theresponse window is running, the wireless device may monitor a PDCCH in afirst coreset. The first coreset may be associated with the BFRprocedure. In an example, the wireless device may monitor the PDCCH inthe first coreset in condition of transmitting the at least first BFRsignal. The wireless device may receive a first DCI via the PDCCH in thefirst coreset when the response window is running. The wireless devicemay consider the BFR procedure successfully completed when receiving thefirst DCI via the PDCCH in the first coreset before the response windowexpires. The wireless device may stop the first timer if configured inresponse to the BFR procedure successfully being completed. The wirelessdevice may stop the response window in response to the BFR proceduresuccessfully being completed.

In an example, when the response window expires, and the wireless devicedoes not receive the DCI, the wireless device may, increment atransmission number, wherein, the transmission number is initialized toa first number (e.g., 0) before the BFR procedure is triggered. If thetransmission number indicates a number less than the configured maximumtransmission number, the wireless device may repeat one or more actionscomprising at least one of: a BFR signal transmission; starting theresponse window; monitoring the PDCCH; incrementing the transmissionnumber if no response received during the response window is running. Ifthe transmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed.

A MAC entity of a wireless device may be configured by an RRC with abeam failure recovery procedure. The beam failure recovery procedure maybe used for indicating to a serving base station of a new SSB or CSI-RSwhen a beam failure is detected. The beam failure may be detected on oneor more serving SSB(s)/CSI-RS(s) of the serving base station. In anexample, the beam failure may be detected by counting a beam failureinstance indication from a lower layer of the wireless device (e.g. PHYlayer) to the MAC entity.

In an example, an RRC may configure a wireless device with one or moreparameters in BeamFailureRecoveryConfig for a beam failure detection andrecovery procedure. The one or more parameters may comprisebeamFailureInstanceMaxCount for a beam failure detection;beamFailureDetectionTimer for the beam failure detection;beamFailureCandidateBeamThreshold: an RSRP threshold for a beam failurerecovery; preamblePowerRampingStep for the beam failure recovery;preambleReceivedTargetPower for the beam failure recovery; preambleTxMaxfor the beam failure recovery; and ra-ResponseWindow. Thera-ResponseWindow may be a time window to monitor one or more responsesfor the beam failure recovery using a contention-free Random Accesspreamble.

In an example, a wireless device may use at least one UE variable for abeam failure detection. BFI_COUNTER may be one of the at least one UEvariable. The BFI_COUNTER may be a counter for a beam failure instanceindication. The BFI_COUNTER may be initially set to zero.

In an example, if a MAC entity of a wireless device receives a beamfailure instance indication from a lower layer (e.g. PHY) of thewireless device, the wireless device may start or restartbeamFailureDetectionTimer. In addition to starting or restarting thebeamFailureDetectionTimer, the wireless device may increment BFI_COUNTERby one. In an example, the wireless device may initiate a random accessprocedure (e.g. on an SpCell) in response to the BFI_COUNTER being equalto beamFailureInstanceMaxCount+1. The wireless device may apply the oneor more parameters in the BeamFailureRecoveryConfig in response to theinitiating the random access procedure. In an example, if thebeamFailureDetectionTimer expires, the wireless device may set theBFI_COUNTER to zero. In an example, if the random access procedure issuccessfully completed, the wireless device may consider the beamfailure recovery procedure successfully completed.

If a MAC entity of a wireless device transmits a contention-free randomaccess preamble for a beam failure recovery request (BFRQ), the MACentity may start ra-ResponseWindow at a first PDCCH occasion from theend of the transmitting the contention-free random access preamble. Thera-ResponseWindow may be configured in BeamFailureRecoveryConfig. Whilethe ra-ResponseWindow is running, the wireless device may monitor atleast one PDCCH (e.g. of an SpCell) for a response to the beam failurerecovery request. The beam failure recovery request may be identified bya C-RNTI.

In an example, if a MAC entity of a wireless device receives, from alower layer of the wireless device, a notification of a reception of atleast one PDCCH transmission and if the at least one PDCCH transmissionis addressed to a C-RNTI and if a contention-free random access preamblefor a beam failure recovery request is transmitted by the MAC entity,the wireless device may consider a random access procedure successfullycompleted.

In an example, a wireless device may initiate a contention-based randomaccess preamble for a beam failure recovery request. When the wirelessdevice transmits Msg3, a MAC entity of the wireless device may startra-ContentionResolutionTimer. The ra-ContentionResolutionTimer may beconfigured by RRC. In response to the starting thera-ContentionResolutionTimer, the wireless device may monitor at leastone PDCCH while the ra-ContentionResolutionTimer is running. In anexample, if the MAC entity receives, from a lower layer of the wirelessdevice, a notification of a reception of the at least one PDCCHtransmission; if a C-RNTI MAC-CE is included in the Msg3; if a randomaccess procedure is initiated for a beam failure recovery and the atleast one PDCCH transmission is addressed to a C-RNTI of the wirelessdevice, the wireless device may consider the random access proceduresuccessfully completed. In response to the random access procedure beingsuccessfully completed, the wireless device may stop thera-ContentionResolutionTimer.

In an example, if a random access procedure of a beam failure recoveryis successfully completed, the wireless device may consider the beamfailure recovery successfully completed.

A wireless device may be configured, for a serving cell, with a firstset of periodic CSI-RS resource configuration indexes by higher layerparameter Beam-Failure-Detection-RS-ResourceConfig. The wireless devicemay further be configured with a second set of CSI-RS resourceconfiguration indexes and/or SS/PBCH block indexes by higher layerparameter Candidate-Beam-RS-List. In an example, the first set and/orthe second set may be used for radio link quality measurements on theserving cell. If a wireless device is not provided with higher layerparameter Beam-Failure-Detection-RS-ResourceConfig, the wireless devicemay determine a first set to include SS/PBCH block indexes and periodicCSI-RS resource configuration indexes. In an example, the SS/PBCH blockindexes and the periodic CSI-RS resource configuration indexes may bewith same values as one or more RS indexes in one or more RS sets. In anexample, the one or more RS indexes in the one or more RS sets may beindicated by one or more TCI states. In an example, the one or more TCIstates may be used for respective control resource sets that thewireless device is configured for monitoring PDCCH. The wireless devicemay expect a single port RS in the first set.

In an example, a first threshold (e.g. Qout,LR) may correspond to afirst default value of higher layer parameterRLM-IS-OOS-thresholdConfig. In an example, a second threshold (e.g.Qin,LR) may correspond to a second default value of higher layerparameter Beam-failure-candidate-beam-threshold. A physical layer in thewireless device may assess a first radio link quality according to thefirst set of periodic CSI-RS resource configurations against the firstthreshold. For the first set, the wireless device may assess the firstradio link quality according to periodic CSI-RS resource configurationsor SS/PBCH blocks. In an example, the periodic CSI-RS resourceconfigurations or the SS/PBCH blocks may be associated (e.g. quasico-located) with at least one DM-RS of PDCCH monitored by the wirelessdevice.

In an example, the wireless device may apply the second threshold to afirst L1-RSRP for SS/PBCH blocks. The wireless device may apply thesecond threshold to a second L1-RSRP for periodic CSI-RS resources afterscaling a respective CSI-RS reception power with a value provided byhigher layer parameter Pc_SS.

In an example, a physical layer in a wireless device may, in slots wherethe first radio link quality according to the first set is assessed,provide an indication to higher layers (e.g. MAC). The wireless devicemay provide an indication to higher layers when the first radio linkquality for all corresponding resource configurations in the first setis worse than the first threshold. The wireless device may use the allcorresponding resource configurations in the first set to assess thefirst radio link quality. The physical layer may inform the higherlayers (e.g. MAC, RRC) when the first radio link quality is worse thanthe first threshold with a first periodicity. The first periodicity maybe determined by a maximum between the shortest periodicity of periodicCSI-RS configurations or SS/PBCH blocks in the first set and X (e.g. 10ms).

In an example, in response to a request from higher layers (e.g. MAC), awireless device may provide to the higher layers the periodic CSI-RSconfiguration indexes and/or SS/PBCH block indexes from the second set.The wireless device may further provide, to the higher layers,corresponding L1-RSRP measurements that are larger than or equal to thesecond threshold.

A wireless device may be configured with one control resource set(coreset) by higher layer parameterBeam-failure-Recovery-Response-CORESET. The wireless device may befurther configured with an associated search space provided by higherlayer parameter search-space-config. The associated search space may beused for monitoring PDCCH in the one control resource set. The wirelessdevice may receive from higher layers (e.g. MAC), by parameterBeam-failure-recovery-request-RACH-Resource, a configuration for a PRACHtransmission. For the PRACH transmission in slot n and according toantenna port quasi co-location parameters associated with periodicCSI-RS configuration or SS/PBCH block with a first RS index, thewireless device may monitor the PDCCH for detection of a DCI formatstarting from slot n+4 within a window. The window may be configured byhigher layer parameter Beam-failure-recovery-request-window. The DCIformat may be with CRC scrambled by C-RNTI. For a PDSCH reception, thewireless device may assume the antenna port quasi-collocation parameters(e.g. as for monitoring the PDCCH) until the wireless device receives byhigher layers an activation for a TCI state or a parameterTCI-StatesPDCCH.

In an example, if a BWP inactivity timer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not an initial BWP: if a PDCCHaddressed to C-RNTI or CS-RNTI indicating downlink assignment or uplinkgrant is received on the active BWP: if there is not an ongoing randomaccess procedure associated with the activated Serving Cell, the MACentity may start or restart the BWP inactivity timer associated with theactive DL BWP.

In an example, if a BWP inactivity timer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not an initial BWP: if aMAC-PDU is transmitted in a configured uplink grant or received in aconfigured downlink assignment; if there is not an ongoing random accessprocedure associated with the activated Serving Cell, the MAC entity maystart or restart the BWP inactivity timer associated with the active DLBWP.

In an example, if a BWP inactivity timer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not an initial BWP: if a PDCCHaddressed to a C-RNTI is received on the active DL BWP: if an ongoingrandom access procedure associated with the activated Serving Cell issuccessfully completed in response to receiving the PDCCH addressed tothe C-RNTI, the MAC entity may start or restart the BWP inactivity timerassociated with the active DL BWP.

Example of a Beam Failure on SCell

In an example, a base station may transmit, to a wireless device, one ormore messages comprising configuration parameters of one or more cells.The one or more cells may comprise at least one PCell/PSCell and one ormore SCells. In an example, an SpCell (e.g., PCell or PSCell) and one ormore SCells may operate on different frequencies and/or different bands.In an example, an SCell may support a multi-beam operation. In themulti-beam operation, a wireless device may perform one or more beammanagement procedures (e.g., a beam failure recovery procedure) on theSCell. The wireless device may perform a beam failure recovery (BFR)procedure when at least one of one or more beam pair links between theSCell and the wireless device fails. Existing BFR procedures may resultin inefficiencies when there is a beam failure for one of the one ormore SCells.

Example embodiments enhance existing BFR procedures to improve downlinkradio efficiency and reduce uplink signaling overhead when there is abeam failure for an SCell. In an example, downlink signaling processesare enhanced for recovery of a beam failure for an SCell. In an example,uplink signaling is enhanced for recovery a beam failure for an SCell.Example embodiments provide processes for a wireless device and a basestation to enhance a beam failure recovery (BFR) procedure for an SCell.

When there is a beam failure on an SCell, a wireless device may notreceive a DCI (e.g. a downlink assignment or an uplink grant) on atleast one PDCCH in one or more coresets of the SCell. In response to notreceiving the DCI, the wireless device may not restartSCellDeactivationTimer. In an example, an expiry of theSCellDeactivationTimer may occur before a base station expects theSCellDeactivationTimer to expire. The base station may not be aware ofthe expiry of the SCellDeactivationTimer.

The wireless device may deactivate the SCell in response to the expiryof the SCellDeactivationTimer. In an example, the deactivating the SCellmay result in an interruption of an ongoing BFR procedure. In anexample, in response to the deactivating the SCell, the base station mayreactivate the SCell (via SCell Activation/Deactivation MAC-CE). Thereactivating the SCell may result in unnecessary signaling and overhead.In an example, recovering a beam failure on the SCell via the ongoingBFR procedure may be faster than the deactivating and the reactivatingthe SCell.

Example embodiments enhance existing BFR procedures to improve downlinkradio efficiency and reduce uplink signaling overhead when carrieraggregation (CA) is configured for a wireless device.

Example of a Beam Failure on BWP

A base station may configure a wireless device with one or more BWPs toachieve a bandwidth adaptation (BA). For example, a base station mayindicate, to a wireless device, which of the one or more (configured)BWPs is an active BWP. The active BWP may comprise an active UL BWPand/or an active DL BWP configured by a higher layer (e.g. RRC).

In an example paired spectrum (e.g., FDD), a gNB and/or a wirelessdevice may switch to an active DL BWP and an active UL BWPindependently. In an example unpaired spectrum (e.g., TDD), a gNB and/ora wireless device may switch to an active DL BWP and an active UL BWPsimultaneously. A wireless device may perform BWP switching between oneor more (configured) BWPs, in response to receiving a DCI (e.g., BWPswitching DCI), or in response to a BWP inactivity timer expiring, or inresponse to initiating a random access procedure.

In an example, when configured with a BWP inactivity timer for a servingcell, a wireless device may switch to a default DL BWP, in response toan expiry of the BWP inactivity timer. The default DL BWP may beconfigured by a network. The switching the active DL BWP to the defaultDL BWP may activate the default DL BWP and/or deactivate the active DLBWP.

In existing beam recovery procedures, when a wireless device detects abeam failure on an active BWP, the wireless device may initiate a BFRprocedure for the active BWP. In an example, while the BFR procedure isongoing, the wireless device may miss a DCI transmitted from a basestation. In response to the missing the DCI, a first BWP inactivitytimer at the wireless device and a second BWP inactivity timer at abase-station for the wireless device may become out of synchronization.The base station may not identify on which DL BWP the wireless device isoperating (e.g. active DL BWP or active DL/UL BWP pair). The basestation may transmit a downlink signal (e.g. RAR, DCI) on a BWP whichmay be deactivated by the wireless device due to the first BWPinactivity timer expiring. This misalignment may lead to unnecessarydelays, data losses or signaling overhead.

In an example, during a BFR procedure, misalignment on which BWP is anactive BWP at a base station and a wireless device may occur when thewireless device misses a DCI transmitted from the base station. In anexample, the DCI may indicate BWP switching. In an example, the DCI mayindicate an uplink grant or a downlink assignment which may restart aBWP inactivity timer. The base station may not be aware that thewireless device misses detecting the DCI for BWP switching. Recoveryfrom the misalignment caused by the wireless device missing the DCI forBWP switching may result in a transmission delay and signaling overhead.

In an example, due to misalignment on an active BWP between a wirelessdevice and a base station, the base station may not be aware of anexpiry of an BWP inactivity timer. In an example, the wireless devicemay switch from an active DL BWP to a default DL BWP in response to theexpiry of the BWP inactivity timer. The base station may assume thewireless device operating on the active DL BWP. In response to receivinga beam failure recovery request (BFRQ) signal (e.g., preamble) via anactive UL BWP for a BFR procedure of the active DL BWP, the base stationmay not know on which DL BWP a response of the BFRQ signal istransmitted. In an example, the base station may transmit the responseon the active DL BWP, which the wireless device may not be monitoring.This may increase the latency of the BFR procedure. In an example, thebase station may transmit the response of the BFRQ signal on both theactive DL BWP and the default DL BWP. This may result in a waste ofradio resource for redundant transmission of the response.

In an example embodiment, a wireless device may perform one or more beammanagement procedures (e.g., a BFR procedure) on an active BWP. Thewireless device may perform a BFR procedure when at least one of one ormore beam pair links of the wireless device on the active BWP fails.There is a need to improve existing BFR procedures. Example embodimentsenhance existing BFR procedures to improve downlink radio efficiency andreduce uplink signaling overhead when BWPs are configured for a cell.

In an example embodiment, uplink resources/configuration of a BFRQsignal on a first UL BWP may be linked to a first DL BWP. The linkagemay be implicit or explicit. The wireless device may monitor a responseof the BFRQ signal on the first DL BWP. The first DL BWP may bedifferent than the active DL BWP. The wireless device may performswitching to the first DL BWP for monitoring the response of the BFRQsignal in response to transmitting the BFRQ signal.

In an example embodiment, linking between a UL BWP (e.g., non-initial)and a DL BWP (e.g., non-initial) may be introduced to reduce redundanttransmissions of a response of a BFRQ signal. This may reduce networkcomplexity. In an example, a first UL BWP may be linked with a first DLBWP. A wireless device may transmit a first preamble for a BFR procedurevia the first UL BWP. The first preamble may be a BFRQ signal of a BFRprocedure. In response to receiving the first preamble, the base stationmay transmit a response of the first preamble on the first DL BWP. In anexample, a wireless device may be active on a second DL BWP on which atleast a beam failure is identified. In response to transmitting thefirst preamble via the first UL BWP, the wireless device may switch fromthe second DL BWP to the first DL BWP to receive a response of the firstpreamble. In an example, the wireless device may switch from the secondDL BWP to the first DL BWP before the transmitting the first preamble.

In an example, the second DL BWP may not be an initial BWP. In anexample, the second DL BWP may not be a default DL BWP. In an example,the linkage may be indicated to the wireless device via systeminformation. In an example, the linkage may be controlled by a networkin an implicit way (i.e., left to the network's implementation).

In response to the switching, the wireless device may start monitoring,for a DCI, on at least one PDCCH in one or more coresets of the first DLBWP. The DCI may be a response of the BFRQ signal. In response toreceiving the DCI, the BFR procedure may be successfully completed.

In an example embodiment, in response to an expiry of an BWP inactivitytimer during an ongoing BFR procedure, the wireless device may switch anactive BWP to a default BWP. In an example, in response to the switchingthe active BWP, the wireless device may stop or abort the ongoing BFRprocedure. It may be desirable for the wireless device to switch to thedefault BWP, when the default BWP has a small coreset. Monitoring thesmall coreset on the default BWP may reduce power consumption of thewireless device. In an example, a second PDCCH in a coreset of thedefault BWP may not have a beam failure. The second PDCCH of the defaultBWP may be robust against a beam failure. In an example, a firstprobability of missing a first DCI in one or more first coresets of theactive BWP may be higher than a second probability of missing a secondDCI in one or more second coresets of the default BWP.

In an example, in response to switching from an active BWP to a defaultBWP, a wireless device may start monitoring at least one second PDCCH inone or more coresets of the default BWP. In an example, in response toswitching the active BWP, the wireless device may initiate an uplinktransmission (e.g. RACH). The base station may be aware of the wirelessdevice switching the active BWP in response to receiving the uplinktransmission via the default BWP. In an example, the wireless device maytransmit a CSI report based on measurement of a CSI-RS resourceassociated to the default BWP. In response to receiving the CSI report,the base station may be aware of the default BWP that the wirelessdevice is operating.

In an example embodiment, in response to initiating a BFR procedure, awireless device may stop a BWP inactivity timer to avoid an unpredictedbehavior between a base station and the wireless device. The stoppingthe BWP inactivity timer during the BFR procedure may avoid implicit BWPswitching during the BFR procedure. When a base station receives a BFRQsignal (e.g., preamble) for the BFR procedure, the base station may beaware of the BFR procedure of a DL BWP. The DL BWP may be an active DLBWP that the wireless device is operating on. In response to receivingthe BFRQ signal, the base station may transmit a response of the BFRQsignal on the DL BWP. In an example, the wireless device may restart theBWP inactivity timer in response to receiving the response of the BFRQsignal.

In an example, when one or more downlink control channels of an activeDL BWP of a serving cell recover during a random access procedure for abeam failure recovery, a wireless device may receive at least one PDCCH.In an example, the at least one PDCCH may be addressed to a C-RNTI ofthe wireless device. In an example, the at least one PDCCH may beaddressed to a CS-RNTI of the wireless device. In response to receivingthe at least one PDCCH, the wireless device may stop the random accessprocedure for the beam failure recovery. In response to stopping therandom access procedure, the wireless device may restart thebandwidthPartInactivityTimer associated with the active DL BWP.

In an example, when one or more downlink control channels of an activeDL BWP of a serving cell recover during a random access procedure for abeam failure recovery, a wireless device may receive at least one MACPDU. The at least one MAC PDU may be received in a configured downlinkassignment. In response to receiving the at least one MAC PDU, thewireless device may stop the random access procedure for the beamfailure recovery. In response to stopping the random access procedure,the wireless device may restart the bandwidthPartInactivityTimerassociated with the active DL BWP.

Example embodiments may reduce a duration of a random access procedurefor a beam failure recovery. This may reduce battery power consumption.Example embodiments may reduce a duration of activity in an active DLBWP. In an example, the active DL BWP may have a wider bandwidth than adefault DL BWP. The monitoring the active DL BWP may result in a highpower consumption (e.g. battery). RestartingbandwidthPartInactivityTimer may be used to switch the wireless devicefrom the active DL BWP to the default DL BWP. This may reduce batterypower consumption.

FIG. 22 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure. FIG. 23 is a flow diagram of the downlink beam failurerecovery procedure disclosed in FIG. 22 . In FIG. 22 , a wireless devicemay receive one or more messages comprising configuration parameters intime T0. The one or more messages may comprise one or more RRC messages(e.g. RRC connection reconfiguration message, or RRC connectionreestablishment message, or RRC connection setup message). In anexample, the configuration parameters may comprise bandwidth part (BWP)configuration parameters for a plurality of BWPs comprising a first BWP(e.g., default BWP) and a second BWP (e.g., non-default BWP). Theconfiguration parameters may further comprise one or more beam failurerecovery (BFR) configuration parameters. The one or more BFRconfiguration parameters may comprise a first set of RS resourceconfigurations for the second BWP. The first set of RS resourceconfigurations may comprise one or more first RSs (e.g., CSI-RS or SSblocks) of the second BWP. The one or more BFR configuration parametersmay further comprise a second set of RS resource configurationscomprising one or more second RSs (e.g., CSI-RS or SS blocks) of thesecond BWP. The wireless device may measure radio link quality of one ormore beams associated with the one or more first RSs and/or the one ormore second RSs. The one or more BFR configuration parameters mayfurther comprise one or more beam failure recovery request (BFRQ)resources associated with the second BWP. In an example, the one or moreBFR configuration parameters may further comprise an association betweeneach of the one or more second RSs and each of the one or more BFRQresources.

In an example, a wireless device may receive a first DCI indicatingswitching a current active BWP from a first BWP to a second BWP. In anexample, the first DCI may comprise a BWP indicator. The wireless devicemay determine that the first DCI indicates BWP switching in response tothe BWP indicator indicating a BWP different from the current activeBWP. At time T1, the wireless device may start a first timer in responseto switching the current active BWP from the first BWP to the secondBWP.

In an example, the wireless device may assess a first radio link qualityof the one or more first RSs (First RS 1 and First RS 2 in FIG. 22 ) ofthe second BWP against a first threshold. In an example, the firstthreshold (e.g. hypothetical BLER, L1-RSRP) may be a first valueprovided by a higher layer (e.g. RRC, MAC). The wireless device maymonitor at least one PDCCH of the second BWP. At least one RS (e.g.,DM-RS) of the at least one PDCCH may be associated with (e.g., QCLed)the one or more first RSs.

A wireless device may detect a beam failure on the second BWP when thefirst radio link quality of the one or more first RSs meets certaincriteria. For example, a beam failure may occur when RSRP/SINR of theone or more first RSs is lower than the first threshold and/or BLER ishigher than the first threshold. The assessment may be for a consecutivenumber of times with a value provided by a higher layer (e.g. RRC, MAC).

In response to detecting the beam failure on the second BWP, thewireless device may initiate a random access procedure for a beamfailure recovery (BFR) procedure for the second BWP (time T2 in FIG. 22). In response to initiating the BFR procedure, the wireless device maystart a second timer (e.g., if configured) and/or initiate a candidatebeam identification procedure. For the candidate beam identificationprocedure, the wireless device may identify a first RS in the one ormore second RSs. The first RS (Second RS 2 in FIG. 22 ) may beassociated with a BFRQ resource of the one or more BFRQ resources. TheBFRQ resource may comprise at least one preamble and at least one PRACH(e.g. time and/or frequency) resource. In an example, a second radiolink quality (e.g. BLER, L1-RSRP) of the first RS may be better (e.g.lower BLER or higher L1-RSRP or higher SINR) than a second threshold. Inthe example, the second threshold may be a second value provided by thehigher layer (e.g. RRC, MAC).

In an example, in response to detecting the beam failure on the secondBWP and identifying the first RS of the second BWP, the wireless devicemay transmit, in a first slot, the at least one preamble via the atleast one PRACH resource for a BFR procedure of the second BWP (time T3in FIG. 22 ). In response to transmitting the at least one preamble inthe first slot, the wireless device may start, from a second slot,monitoring for a BFR response. The monitoring for the BFR response maycomprise monitoring at least one second PDCCH in one or more coresetsfor a second DCI (e.g. a downlink assignment or an uplink grant) withina configured response window. The second DCI may be with CRC scrambledby a C-RNTI of the wireless device. The at least one second PDCCH in oneor more coresets may or may not be on the second BWP.

In an example, in response to receiving the second DCI on the at leastone second PDCCH in the one or more coresets, within the configuredresponse window, the random access procedure for the BFR procedure maybe successfully completed (time T4 in FIG. 22 ).

In an example, a wireless device may initiate a BFR procedure inresponse to detecting at least one beam failure indication of an activeDL BWP. The at least one beam failure may be associated with at leastone downlink control channels of the active DL BWP. In an example, anBWP inactivity timer may expire while the BFR procedure is ongoing (e.g.before a random access procedure for a BFR procedure is initiated). Inan example, in response to an expiry of an BWP inactivity timer whilethe BFR procedure is ongoing, the wireless device may switch the activeDL BWP to a default DL BWP.

In an example, in a paired spectrum (e.g., FDD system), a wirelessdevice may only switch an active DL BWP to a default DL BWP in responseto an expiry of an BWP inactivity timer. The BWP inactivity timer may beassociated with the active DL BWP.

In an example, the wireless device may transmit at least one preamblevia at least one PRACH resource for the BFR procedure on an active ULBWP. The active UL BWP may be active before the expiry of the BWPinactivity timer. When the wireless device switches to the default DLBWP, the wireless device may not monitor the at least one downlinkcontrol channels of the active DL BWP. In an example, the wirelessdevice may start monitoring at least one second downlink controlchannels of the default DL BWP in response to the switching to thedefault DL BWP.

In an example embodiment, the wireless device may stop the beam failurerecovery procedure associated with the at least one downlink controlchannels of the active DL BWP in response to the switching to thedefault DL BWP. In an example, in response to an expiry of an BWPinactivity timer while a BFR procedure is ongoing (i.e., after detectinga beam failure), a wireless device may stop or abort the ongoing beamfailure recovery procedure.

In an example, a base station may not transmit a DCI indicating adownlink assignment or an uplink grant during an ongoing BFR procedure.A BWP inactivity timer may expire during the ongoing BFR procedure. Awireless device may switch an active BWP to a default BWP in response tothe BWP inactivity timer being expired. The base station may be aware ofthe wireless device switching the active BWP to the default BWP due tothe aligned BWP inactivity timer being expired. The base station maytransmit a DCI on the default BWP. The wireless device may monitor atleast one second downlink control channels of the default DL BWP. Theembodiment may avoid a DL data loss and reduce signaling overhead andlatency used on beam failure recovery.

In an example, during the BFR procedure triggered on an active DL BWP, awireless device may not receive a DCI (e.g. a downlink assignment or anuplink grant) on at least one PDCCH in one or more coresets of theactive DL BWP. The wireless device may not restart a BWP inactivitytimer, which may result in the BWP inactivity timer being expired. TheBWP inactivity timer being expired at the wireless device may be notknown to the base station. Example embodiment may solve the misalignmentcaused by the wireless device missing the DCI.

In an example, in response to the expiry of the BWP inactivity timer,the wireless device may switch the active BWP to a default BWP. In anexample, in response to the switching the active BWP, the wirelessdevice may stop or abort the BFR procedure. The wireless device maystart monitoring at least one second PDCCH in one or more coresets ofthe default BWP. In an example, the base station may transmit a DCI onthe one or more coresets of the active BWP. The wireless device may missthe DCI. This may result in a DL data loss. In an example, in responseto switching the active BWP, the wireless device may initiate an uplinktransmission (e.g. RACH). The base station may be aware of the wirelessdevice switching the active BWP in response to receiving the uplinktransmission.

In legacy systems, the wireless device may not stop a BWP inactivitytimer when the wireless device transmits an uplink signal (e.g., UCI,SR) via uplink control channels for BFR procedure. In an exampleimplementation, the BWP inactivity timer keeps running (until it isexpired) when the wireless device transmits an uplink signal (e.g., UCI,SR) via uplink control channels for BFR procedure. The BFR procedure maycontinue after the BWP inactivity timer expires. The wireless device mayswitch from an active BWP (e.g., non-default BWP) to a default BWP basedon an expiry of the BWP inactivity timer. Continuing the BFR procedurefor a BWP in the default BWP may create inefficiencies if the basestation does not switch the wireless device back to the active BWP (theBWP) from the default BWP within a relatively short time (e.g., 5 ms, 20ms, etc.). The wireless device may transmit uplink signals for the BFRprocedure in the default BWP if the wireless device continues the BFRprocedure for the BWP in the default BWP. This may result in increasedinterference to other cells and/or users. The wireless device maymonitor downlink control channels of the default BWP for the BFRprocedure if the wireless device continues the BFR procedure for the BWPin the default BWP. This may result in increased power and/or batteryconsumption of the wireless device. There is a need to implement anenhanced procedure for the BFR of the wireless device.

Example embodiments implements an enhanced BFR procedure for a BWP, forexample, when a PUCCH based BFR procedure is initiated. A wirelessdevice may continue running a BWP inactivity timer when a PUCCH basedBFR is initiated. The wireless device may abort the ongoing BFRprocedure for an active BWP when the BWP inactivity timer expires duringthe BFR procedure. The wireless device may switch to the default BWPfrom the active BWP based on expiry of the BWP inactivity timer. Thisenhanced process improves uplink control signaling, reduces uplinkoverhead and interference, and reduces wireless device battery powerconsumption.

FIG. 24 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure. FIG. 25 is a flow diagram of the downlink beam failurerecovery procedure disclosed in FIG. 24 . A wireless device may receiveone or more messages comprising configuration parameters at time T0. Inan example, the configuration parameters may comprise BWP configurationparameters for a plurality of BWPs comprising a first BWP (e.g., defaultBWP) and a second BWP (e.g., non-default BWP). The configurationparameters may further comprise BFR configuration parameters comprisingone or more first RSs. The first BWP may be a current active BWP of acell. In an example, a wireless device may receive a DCI indicatingswitching the current active BWP from the first BWP to the second BWP.In an example, the DCI may comprise a BWP indicator. The wireless devicemay determine that the DCI indicates BWP switching in response to theBWP indicator indicating a BWP different from the current active BWP. Attime T1, the wireless device may start a first timer in response toswitching the current active BWP from the first BWP to the second BWP.

In an example, the wireless device may initiate a BFR procedure for thesecond BWP in response to detecting a beam failure based on one or morefirst RSs (First RS 1 and First RS 2 in FIG. 24 ) of the second BWP(time T2 in FIG. 24 ). In response to initiating the BFR procedure, thewireless device may start a second timer (e.g., if configured). At timeT3, the first timer may expire while the BFR procedure is ongoing. In anexample, the wireless device may stop/abort the BFR procedure for thesecond BWP in response to the expiry of the first timer at T3. In anexample, the wireless device may stop/reset the second timer. At timeT4, the wireless device may switch the current active BWP from thesecond BWP to the first BWP in response to the stopping/aborting the BFRprocedure.

In an example, the wireless device may initiate an uplink transmissionvia the first BWP in response to the switching the current active BWP.In an example, the wireless device may monitor at least one PDCCH of thefirst BWP in response to the switching the current active BWP. The basestation may be aware of the wireless device operating on the first BWP.The base station may transmit a DCI (e.g. uplink grant or a downlinkassignment) on the first BWP. This may reduce a DL data loss of thewireless device. In an example, this may reduce a latency of a datatransmission.

In an example, a default BWP may have a narrow bandwidth. In an example,an active DL BWP may have a wide bandwidth. When a wireless device ismonitoring the active DL BWP for a long time without activity, thewireless device may move to the default BWP (e.g. default UL BWP and/ordefault DL BWP) for power saving. In an example, monitoring for a DCI inthe narrow bandwidth (e.g. default BWP) may reduce power consumption.Monitoring the wide bandwidth until receiving the DCI may not be powerefficient. Example embodiment may provide a mechanism to reduce a powerconsumption for the wireless device.

In an example, a wireless device may receive, from a base station, oneor more messages comprising one or more configuration parameters. Theone or more configuration parameters may indicate at least one of aplurality of bandwidth parts (BWPs) and a first value of a first BWPinactivity timer. The plurality of BWPs may comprise a first BWP and asecond BWP. In an example, the one or more configuration parameters mayfurther indicate at least one of: one or more first reference signals ofthe first BWP; one or more second RSs of the first BWP; and one or morebeam failure recovery request (BFRQ) resources on the first BWP. In anexample, the one or more configuration parameters may further indicatean association between each of the one or more second RSs and each ofthe one or more BFRQ resources. In an example, the one or more first RSsmay comprise one or more first CSI-RSs and/or one or more first SSblocks. In an example, the one or more second RSs may comprise one ormore second CSI-RSs and/or one or more second SS blocks.

In an example, the wireless device may start the first BWP inactivitytimer with the first value in response to switching to the first BWP asan active BWP. In an example, the wireless device may initiate a randomaccess procedure for a beam failure recovery in response to reaching anumber of beam failure instance indications for the first BWP. In anexample, the number of beam failure instance indications may beconfigured by a higher layer (e.g. RRC). In an example, the beam failureinstance indications may comprise an indication of a beam failureinstance from a physical layer of the wireless device to a medium-accesslayer of the wireless device. The beam failure instance may compriseassessing the one or more first RSs with radio quality lower than afirst threshold. In an example, the first threshold may be based onhypothetical BLER, or RSRP, or RSRQ, or SINR.

In an example, the random access procedure may comprise selecting aselected RS, in the one or more second RSs. The selected RS may beassociated with a BFRQ resource. In an example, the BFRQ resource may beone of the one or more BRFQ resources. In an example, the BFRQ resourcemay comprise at least one preamble and at least one random accesschannel resource. The random access procedure may further comprisetransmitting, by the wireless device, the at least one preamble via theat least one random access channel resource. The at least one randomaccess channel resource may comprise one or more time resources and/orone or more frequency resources. In an example, the selected RS may beassociated with one of the one or more second RSs with radio qualityhigher than a second threshold. The second threshold may be based onL1-RSRP, or RSRQ, or hypothetical BLER, or SINR.

In an example, the wireless device may stop or abort the beam failurerecovery in response to an expiry of the first BWP inactivity timer. Inan example, the wireless device may switch the first BWP to the secondBWP as the active BWP in response to the expiry of the first BWPinactivity timer. The wireless device may start monitoring, for acontrol information, a downlink control channel of the second BWP. In anexample, the wireless device may initiate an uplink transmission (e.g.RACH) on the second BWP.

In an example embodiment, the wireless device may stop a BWP inactivitytimer of a cell based on the initiation of a BFR procedure usingrandom-access procedure associated with the cell. In an exampleembodiment, the wireless device may stop the BWP inactivity timer basedon the initiation of a random-access procedure for a BFR. In an exampleembodiment, the BWP inactivity timer does not expire during a RACH basedBFR procedure.

In legacy systems, the wireless device may not stop a BWP inactivitytimer when the wireless device transmits an uplink signal (e.g., UCI,SR) via uplink control channels for BFR procedure. In an exampleimplementation, the BWP inactivity timer keeps running (until it isexpired) when the wireless device transmits an uplink signal (e.g., UCI,SR) via uplink control channels for BFR procedure. The BFR procedure maycontinue after the BWP inactivity timer expires. The wireless device mayswitch from an active BWP (e.g., non-default BWP) to a default BWP basedon an expiry of the BWP inactivity timer. Continuing the BFR procedurefor a BWP (e.g., the active BWP) in the default BWP may createinefficiencies if the base station does not switch the wireless deviceback to the active BWP (e.g., the BWP) from the default BWP within arelatively short time (e.g., 5 ms, 20 ms, etc.). The wireless device maytransmit uplink signals for the BFR procedure in the default BWP if thewireless device continues the BFR procedure for the BWP in the defaultBWP. This may result in increased interference to other cells and/orusers. The wireless device may monitor downlink control channels of thedefault BWP for the BFR procedure if the wireless device continues theBFR procedure for the BWP in the default BWP. This may result inincreased power and/or battery consumption of the wireless device. Thereis a need to implement an enhanced procedure for the BFR of the wirelessdevice.

Example embodiments implements an enhanced BFR procedure for a BWP, forexample, when a PUCCH based BFR procedure is initiated. In an enhancedBFR procedure, a wireless device may stop running a BWP inactivity timerwhen a PUCCH based BFR is initiated. The wireless device may continuethe ongoing BFR procedure for an active BWP and the BWP inactivity timeris stopped during the BFR procedure. The wireless device may not switchto the default BWP from the active BWP based on expiry of the BWPinactivity timer. This enhanced process improves uplink controlsignaling, reduces uplink overhead and interference, and reduceswireless device battery power consumption.

FIG. 26 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure. FIG. 27 is a flow diagram of the downlink beam failurerecovery procedure disclosed in FIG. 26 . Actions of FIG. 26 at time T0,T1 and/or T2 are similar to actions of FIG. 24 at time T0, T1 and/or T2.A first BWP may be a current active BWP of a cell at time T0. In anexample, a wireless device may receive a first DCI indicating switchinga current active BWP from the first BWP to a second BWP. The wirelessdevice may start a first timer in response to switching the currentactive BWP from the first BWP to the second BWP (time T1 in FIG. 26 ).

In an example, the wireless device may initiate a BFR procedure for thesecond BWP (time T3 in FIG. 26 ) in response to detecting a beam failurebased on one or more first RSs (First RS 1 and First RS2) of the secondBWP (time T2 in FIG. 26 ). In response to initiating the BFR procedure,the wireless device may stop running the first timer. In response to thestopping the running the first timer, the wireless device may refrainfrom switching the current active BWP of the cell due to an expiry ofthe first timer while the BFR procedure is ongoing.

In an example, the wireless device may restart the first timer inresponse to completing the BFR procedure successfully (time T4 in FIG.26 ). The completing the BFR procedure successfully may comprisereceiving a BFR response. The BFR response may comprise a second DCI(e.g. a downlink assignment or an uplink grant) on at least one secondPDCCH in one or more coresets. The one or more coresets may beassociated with the BFR procedure of the second BWP. The second DCI maybe addressed to a C-RNTI of the wireless device.

In an example embodiment, a wireless device may receive, from a basestation, one or more messages comprising one or more configurationparameters. The one or more configuration parameters may indicate atleast one of a plurality of bandwidth parts (BWPs) and a first value ofa first BWP inactivity timer. The plurality of BWPs may comprise a firstBWP. In an example, the one or more configuration parameters may furtherindicate at least one of: one or more first reference signals of thefirst BWP; one or more second RSs of the first BWP; and one or more beamfailure recovery request (BFRQ) resources on the first BWP. In anexample, the one or more configuration parameters may further indicatean association between each of the one or more second RSs and each ofthe one or more BFRQ resources. In an example, the one or more first RSsmay comprise one or more first CSI-RSs and/or one or more first SSblocks. In an example, the one or more second RSs may comprise one ormore second CSI-RSs and/or one or more second SS blocks.

In an example, the wireless device may start the first BWP inactivitytimer with the first value in response to switching to the first BWP asan active BWP. The switching may be controlled via a DCI indicating aBWP switching or an expiry of an inactivity timer.

In an example, in response to reaching a number of beam failure instanceindications for the first BWP, the wireless device may initiate a randomaccess procedure for a beam failure recovery. In an example, in responseto the initiating the random access procedure, the wireless device maystop the first BWP inactivity timer. In an example, the number of beamfailure instance indications may be configured by a higher layer (e.g.RRC). In an example, the beam failure instance indications may comprisean indication of a beam failure instance from a physical layer of thewireless device to a medium-access layer of the wireless device. Thebeam failure instance may comprise assessing the one or more first RSswith radio quality lower than a first threshold. In an example, thefirst threshold may be based on hypothetical BLER, or RSRP, or RSRQ, orSINR.

In an example, the random access procedure may comprise selecting aselected RS, in the one or more second RSs. The selected RS may beassociated with a BFRQ resource. In an example, the BFRQ resource may beone of the one or more BRFQ resources. In an example, the BFRQ resourcemay comprise at least one preamble and at least one random accesschannel resource. The random access procedure may further comprisetransmitting, by the wireless device, the at least one preamble via theat least one random access channel resource of the first BWP. The atleast one random access channel resource may comprise one or more timeresources and/or one or more frequency resources. In an example, theselected RS may be associated with one of the one or more second RSswith radio quality higher than a second threshold. The second thresholdmay be based on L1-RSRP, or RSRQ, or hypothetical BLER, or SINR.

In an example, the wireless device may monitor, for a controlinformation, a downlink control channel of the second BWP. The wirelessdevice may complete the random access procedure for the beam failurerecovery in response to receiving the control information. In anexample, the monitoring the downlink control channel may comprisesearching for the control information in the downlink control channeladdressed for an identifier (e.g. C-RNTI) associated with the wirelessdevice.

In an example, the wireless device may restart the first BWP inactivitytimer in response to the completing the beam failure recovery.

FIG. 28 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure. FIG. 29 is a flow diagram of the downlink beam failurerecovery procedure disclosed in FIG. 28 . Actions of FIG. 28 at time T0,T1 and T2 are similar to actions of FIG. 24 at time T0, T1 and T2. Afirst BWP may be a current active BWP of a cell in time T0. In anexample, a wireless device may receive a first DCI indicating switchingthe current active BWP from the first BWP to a second BWP. The wirelessdevice may start a first timer in response to switching the currentactive BWP from the first BWP to the second BWP (time T1 in FIG. 28 ).

The wireless device may initiate a BFR procedure for the second BWP inresponse to detecting a beam failure based on one or more first RSs(First RS 1 and First RS 2) of the second BWP (time T2 in FIG. 28 ). Inan example, the first timer may expire while the BFR procedure isongoing (time T3 in FIG. 28 ). In an example, the first timer may expirebefore initiating a BFRQ signal (e.g., preamble transmission). The BFRQsignal may be transmitted at time T4 in FIG. 28 . In response to anexpiry of the first timer (time T3 in FIG. 28 ), the wireless device maynot switch the current active BWP of the cell from the second BWP to thefirst BWP (e.g. default BWP). In an example, the wireless device mayrefrain from switching the current active BWP in response to the expiryof the first timer while the BFR procedure is ongoing. The base stationmay transmit a BFR response comprising a second DCI (e.g. a downlinkassignment or an uplink grant) on at least one second PDCCH in one ormore coresets. The one or more coresets may be associated with the BFRprocedure of the second BWP. The wireless device may restart the firsttimer in response to receiving the second DCI.

FIG. 29 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure. FIG. 30 is a flow diagram of the downlink beam failurerecovery procedure disclosed in FIG. 29 . Actions of FIG. 29 at time T0,T1 and T2 are similar to actions of FIG. 24 at time T0, T1 and T2. Afirst BWP may be a current active BWP of a cell (time T0 in FIG. 29 ).In an example, a wireless device may receive a first DCI indicatingswitching the current active BWP from the first BWP to a second BWP. Thewireless device may start a first timer in response to switching thecurrent active BWP from the first BWP to the second BWP (time T1 in FIG.29 ).

The wireless device may initiate a BFR procedure for the second BWP inresponse to detecting a beam failure based on one or more first RSs(First RS 1 and First RS 2) of the second BWP (time T2 in FIG. 29 ). Inan example, the first timer may expire while the BFR procedure isongoing (time T3 and T4 in FIG. 29 ). In response to an expiry of thefirst timer while the BFR procedure is ongoing, the wireless device mayrestart the first timer (time T3 and time T4 in FIG. 29 ). In anexample, the wireless device may restart the first timer until the BFRprocedure is completed (time T5 in FIG. 29 ). The completing the BFRprocedure may comprise receiving a BFR response. The BFR response maycomprise a second DCI addressed to a C-RNTI of the wireless device. Inan example, the wireless device may restart the first timer in responseto the receiving the second DCI.

In an example, the wireless device may switch the current active BWP ofthe cell from the second BWP to the first BWP (e.g. default BWP) inresponse to the expiry of the first timer while the BFR procedure is notongoing (e.g. completed).

FIG. 31 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure. FIG. 32 is a flow diagram of the downlink beam failurerecovery procedure disclosed in FIG. 31 . A wireless device may beconfigured with one or more BWP configuration parameters and one or moreBFR configuration parameters at time T0. The wireless device may beconfigured with a first BWP and a second BWP. In an example, a wirelessdevice may receive a first DCI indicating switching a current active BWPto the first BWP at time T1.

In an example, the wireless device may initiate a BFR procedure for thefirst BWP (time T2 in FIG. 31 ) in response to detecting a beam failurebased on one or more first RSs (First RS 1 and First RS 2) of the firstBWP (time T2 in FIG. 31 ). In response to initiating the BFR procedure,the wireless device may transmit a BFRQ signal (e.g. preamble) via aBFRQ resource of the first BWP at time T3. The BFRQ resource maycomprise at least one preamble and time and frequency resources. In anexample, in response to transmitting the BFRQ signal, the wirelessdevice may switch the current active BWP from the first BWP to thesecond BWP at time T4. The wireless device may switch to the second BWPto receive a BFR response of the BFRQ signal from the base station. Inan example, the BFR response may comprise a second DCI (e.g. a downlinkassignment or an uplink grant).

In an example, completing the BFR procedure successfully may comprisereceiving a BFR response. The completing the BFR procedure successfullymay comprise receiving a second DCI (e.g. a downlink assignment or anuplink grant) on at least one second PDCCH in one or more coresets ofthe second BWP. The second DCI may be addressed to a C-RNTI of thewireless device. In an example, one or more RSs (e.g., DMRS) of the atleast one second PDCCH may be associated (e.g. QCLed) with a serving RSof the second BWP.

A wireless device may receive from a base station one or more messagescomprising one or more configuration parameters. The one or moreconfiguration parameters may indicate a plurality of bandwidth parts(BWPs). The plurality of BWPs may comprise a first BWP and a second BWP.In an example, the one or more configuration parameters may furtherindicate at least one of: one or more first reference signals of thefirst BWP; one or more second RSs of the first BWP; and one or more beamfailure recovery request (BFRQ) resources on the first BWP. In anexample, the one or more configuration parameters may further indicatean association between each of the one or more second RSs and each ofthe one or more BFRQ resources. In an example, the one or more first RSsmay comprise one or more first CSI-RSs and/or one or more first SSblocks. In an example, the one or more second RSs may comprise one ormore second CSI-RSs and/or one or more second SS blocks.

The wireless device may initiate a random access procedure for a beamfailure recovery in response to reaching a number of beam failureinstance indications for the first BWP. In an example, the number ofbeam failure instance indications may be configured by a higher layer(e.g. RRC). In an example, the beam failure instance indications maycomprise an indication of a beam failure instance from a physical layerof the wireless device to a medium-access layer of the wireless device.The beam failure instance may comprise assessing the one or more firstRSs with radio quality lower than a first threshold. In an example, thefirst threshold may be based on hypothetical BLER, or RSRP, or RSRQ, orSINR.

In an example, the random access procedure may comprise selecting aselected RS, in the one or more second RSs. The selected RS may beassociated with a BFRQ resource. In an example, the BFRQ resource may beone of the one or more BRFQ resources. In an example, the BFRQ resourcemay comprise at least one preamble and at least one random accesschannel resource. The random access procedure may further comprisetransmitting, by the wireless device, the at least one preamble via theat least one random access channel resource of the first BWP. The atleast one random access channel resource may comprise one or more timeresources and/or one or more frequency resources. In an example, theselected RS may be associated with one of the one or more second RSswith radio quality higher than a second threshold. The second thresholdmay be based on L1-RSRP, or RSRQ, or hypothetical BLER, or SINR.

In an example, the wireless device may switch from the first BWP to thesecond BWP in response to the transmitting the at least one preamble.The wireless device may monitor, for a control information, a downlinkcontrol channel of the second BWP. The wireless device may complete thebeam failure recovery in response to receiving the control information.In an example, the monitoring the downlink control channel may comprisesearching for the control information in the downlink control channeladdressed for an identifier (e.g. C-RNTI) associated with the wirelessdevice.

FIG. 33 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure. FIG. 34 is a flow diagram of the downlink beam failurerecovery procedure disclosed in FIG. 33 . In FIG. 33 , a wireless devicemay receive one or more messages comprising configuration parameters intime T0. The one or more messages may comprise one or more RRC messages(e.g. RRC connection reconfiguration message, or RRC connectionreestablishment message, or RRC connection setup message). In anexample, the configuration parameters may comprise bandwidth part (BWP)configuration parameters for a plurality of BWPs comprising a first BWP(e.g., default BWP) and a second BWP (e.g., non-default BWP). Theconfiguration parameters may further comprise one or more beam failurerecovery (BFR) configuration parameters. The one or more BFRconfiguration parameters may comprise a first set of RS resourceconfigurations for the second BWP. The first set of RS resourceconfigurations may comprise one or more first RSs (e.g., CSI-RS or SSblocks) of the second BWP. The one or more BFR configuration parametersmay further comprise a second set of RS resource configurationscomprising one or more second RSs (e.g., CSI-RS or SS blocks) of thesecond BWP. The wireless device may measure radio link quality of one ormore beams associated with the one or more first RSs and/or the one ormore second RSs. The one or more BFR configuration parameters mayfurther comprise one or more beam failure recovery request (BFRQ)resources associated with the second BWP. In an example, the one or moreBFR configuration parameters may further comprise an association betweeneach of the one or more second RSs and each of the one or more BFRQresources.

In an example, a wireless device may receive a first DCI indicatingswitching a current active BWP from a first BWP to a second BWP (timeT1). In an example, the first DCI may comprise a BWP indicator. Thewireless device may determine that the first DCI indicates BWP switchingin response to the BWP indicator indicating a BWP different from thecurrent active BWP. At time T1, the wireless device may start a firstinactivity timer in response to switching the current active BWP fromthe first BWP to the second BWP.

The wireless device may assess a first radio link quality of the one ormore first RSs of the second BWP (First RS 1 and First RS 2) against afirst threshold. In an example, the first threshold (e.g. hypotheticalBLER, L1-RSRP) may be a first value provided by a higher layer (e.g.RRC, MAC). The wireless device may monitor at least one PDCCH of thesecond BWP. At least one RS (e.g., DM-RS) of the at least one PDCCH maybe associated with (e.g., QCLed) the one or more first RSs.

A wireless device may detect a beam failure on the second BWP when thefirst radio link quality of the one or more first RSs meets certaincriteria (time T2). For example, a beam failure may occur when RSRP/SINRof the one or more first RSs is lower than the first threshold and/orBLER is higher than the first threshold. The assessment may be for aconsecutive number of times with a value provided by a higher layer(e.g. RRC, MAC).

In response to detecting the beam failure on the second BWP, thewireless device may initiate a random access procedure for a beamfailure recovery (BFR) procedure of the second BWP (time T2). In anexample, the wireless device may stop the first inactivity timer inresponse to initiating the random access procedure. In response toinitiating the BFR procedure, the wireless device may start a secondtimer (if configured) and/or initiate a candidate beam identificationprocedure. For the candidate beam identification procedure, the wirelessdevice may identify a first RS (Second RS 2) in the one or more secondRSs. The first RS may be associated with a BFRQ resource of the one ormore BFRQ resources. The BFRQ resource may comprise at least onepreamble and at least one PRACH (e.g. time and/or frequency) resource.In an example, a second radio link quality (e.g. BLER, L1-RSRP) of thefirst RS may be better (e.g. lower BLER or higher L1-RSRP or higherSINR) than a second threshold. In the example, the second threshold maybe a second value provided by the higher layer (e.g. RRC, MAC).

In an example, in response to detecting the beam failure on the secondBWP and identifying the first RS of the second BWP, the wireless devicemay initiate a beam failure recovery request (BFRQ) transmission. TheBFRQ transmission may comprise transmitting, in a first slot, the atleast one preamble via the at least one PRACH resource for the BFRprocedure of the second BWP (time T3). In an example, in response to theinitiating the BFRQ transmission, the wireless device may stop the firstinactivity timer. In an example, the wireless device may reset the firstinactivity timer in addition to the stopping the first inactivity timer.In response to transmitting the at least one preamble in the first slot,the wireless device may start, from a second slot, monitoring for a BFRresponse. The monitoring for the BFR response may comprise monitoring atleast one second PDCCH in one or more coresets associated with thesecond BWP for a second DCI (e.g. a downlink assignment or an uplinkgrant) within a configured response window. The second DCI may be withCRC scrambled by a C-RNTI of the wireless device.

In an example, in response to receiving the second DCI on the at leastone second PDCCH in the one or more coresets, within the configuredresponse window, the random access procedure for the BFR procedure maybe successfully completed (time T4). In an example, in response tocompleting the random access procedure, the wireless device may restartthe first inactivity timer.

In an example, a base station may configure a wireless device withdownlink control channel(s) (or control resource sets (coresets)). Thewireless device may detect a beam failure based on measuring thedownlink control channel(s). When the quality of the downlink controlchannels is poor (e.g., higher BLER than a threshold), the wirelessdevice may detect a beam failure and initiate a BFR procedure.

The wireless device may keep monitoring downlink control channel(s)during the ongoing BFR procedure. For example, while monitoring thedownlink control channel(s), the obstacle between the base station andthe wireless device causing the beam failure may disappear and/or moveduring the BFR procedure. For example, while monitoring the downlinkcontrol channel(s), a deep fading channel causing the beam failure maydisappear and/or move during the BFR procedure. The downlink controlchannel(s) may recover during the ongoing BFR procedure. For example,the quality of the downlink control channel(s) may become good again(e.g., lower BLER than the threshold) during the BFR procedure. Forexample, the wireless device may receive a downlink control informationvia the downlink control channel(s) during the BFR procedure when thequality of the downlink control channel(s) becomes good again.

In legacy systems, a wireless device may start a BFR procedure when thequality of the channel is below a threshold. When the quality of thedownlink control channel(s) changes to above a threshold (during a BFRprocedure) and the wireless device receives downlink control informationvia the downlink control channel(s), the wireless device may continuethe BFR procedure. The wireless device transmits uplink signals (e.g.,preamble, BFRQ) for the BFR procedure resulting in increased uplinkinterference to other users/cells. The wireless device may continue theBFR procedure wherein the wireless device monitors an additionaldedicated control channel (e.g., coreset) configured for the BFRprocedure increasing the battery consumption of the wireless device.There is a need to develop an enhanced BFR procedure for the wirelessdevice to reduce uplink interference and reduce wireless device batterypower consumption.

In an example embodiment, when the quality of the downlink controlchannel(s) changes to above a certain threshold and the wireless devicereceives downlink control information via the downlink controlchannel(s), the wireless device stops the BFR procedure. When thewireless device receives a DCI via the downlink control channel(s)during the BFR procedure, the wireless device may stop the BFRprocedure. For example, the DCI may be addressed to an identifier. Ifthe identifier is common to a plurality of wireless devices, thewireless device may not determine if the DCI is destined for itself oranother wireless device of the plurality of the wireless devices. Whenthe wireless device receives a DCI via the downlink control channel(s)during the BFR procedure, the wireless device stops the BFR procedure ifthe DCI is addressed to an identifier specific to the wireless device.In an example, the identifier may be a Cell Radio Network TemporaryIdentifier (C-RNTI). In an example, the identifier may be a ConfiguredScheduling Radio Network Temporary Identifier (CS-RNTI). This enhancedBFR procedure reduces uplink interference and reduce wireless devicebattery power consumption.

In legacy systems, the wireless device stops the BWP inactivity timerwhen the wireless device initiates a random-access procedure. In legacysystems, BWP inactivity timer remains stop until the random-accessprocedure is successfully completed. This may result in increasedmis-alignment between timers of a base station and wireless device, forexample, when a random access procedure is stopped or aborted. There isa need to implement an enhanced BWP inactivity timer to reducemis-alignment between timers of a base station and wireless device.

In an example embodiment, when the wireless device stops therandom-access procedure, the wireless device restarts the BWP inactivitytimer. Example embodiments may avoid the BWP misalignment between thewireless device and the base station and/or reduce the gap(misalignment) between the BWP inactivity timers at the wireless deviceand the base station from increasing.

FIG. 35 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure. FIG. 36 is a flow diagram of the downlink beam failurerecovery procedure disclosed in FIG. 35 . Actions in time T0, T1 and T2in FIG. 35 are same as the actions in time T0, T1 and T2 in FIG. 33 . Inan example, a wireless device may stop a first inactivity timer inresponse to initiating a random access procedure for a beam failurerecovery (time T3 in FIG. 35 ). The wireless device may detect a beamfailure on at least one PDCCH of the second BWP at time T2. In anexample, the at least one PDCCH of the second BWP may improve during therandom access procedure for a beam failure recovery. The wireless devicemay monitor the at least one PDCCH before the random access procedure isinitiated (e.g., before T2). In an example, while the random accessprocedure is ongoing, a blockage between a wireless device and a servingcell may not exist. In an example, a beam failure of the second BWP maybe caused by a fading dip (e.g. deep fading). The fading deep may notexist during the random access procedure.

In an example, the wireless device may receive a control information(e.g., DCI) in time T4 on the at least one PDCCH during the randomaccess procedure (e.g. before the random access procedure is completedin time T5). In an example, the wireless device may monitor the at leastone PDCCH and a dedicated coreset during the random access procedure forthe beam failure recovery. The dedicated coreset may be configured bythe one or more messages (at time T0) to the wireless device. Thewireless device monitors the dedicated coreset to receive a BFR responseof a BFRQ transmission. In an example, the at least one PDCCH may beaddressed to a C-RNTI of the wireless device. In an example, the atleast one PDCCH may be addressed to a CS-RNTI of the wireless device. Inresponse to receiving the at least one PDCCH, the wireless device maystop the random access procedure for the beam failure recovery. Inresponse to stopping the random access procedure, the wireless devicemay restart the first inactivity timer associated with the second BWP.

In an example, a wireless device may receive, from a base station, oneor more messages comprising one or more configuration parameters. Theone or more configuration parameters may indicate at least a first valueof a first BWP inactivity timer of a first BWP. In an example, the oneor more configuration parameters may further indicate at least one ofone or more first reference signals of the first BWP; one or more secondRSs of the first BWP; and one or more beam failure recovery request(BFRQ) resources on the first BWP. In an example, the one or moreconfiguration parameters may further indicate an association betweeneach of the one or more second RSs and each of the one or more BFRQresources. In an example, the one or more first RSs may comprise one ormore first CSI-RSs and/or one or more first SS blocks. In an example,the one or more second RSs may comprise one or more second CSI-RSsand/or one or more second SS blocks.

In an example, the wireless device may start the first BWP inactivitytimer in response to switching to the first BWP as an active BWP. Theswitching may be indicated by a DCI or an expiry of an inactivity timer.

The wireless device may initiate a random access procedure for a beamfailure recovery in response to reaching a number of beam failureinstance indications for the first BWP. In an example, the number ofbeam failure instance indications may be configured by a higher layer(e.g. RRC). In an example, the beam failure instance indications maycomprise an indication of a beam failure instance from a physical layerof the wireless device to a medium-access layer of the wireless device.The beam failure instance may comprise assessing the one or more firstRSs with radio quality lower than a first threshold. In an example, thefirst threshold may be based on hypothetical BLER, or RSRP, or RSRQ, orSINR.

In an example, the random access procedure may comprise selecting aselected RS, in the one or more second RSs. The selected RS may beassociated with a BFRQ resource. In an example, the BFRQ resource may beone of the one or more BRFQ resources. In an example, the BFRQ resourcemay comprise at least one preamble and at least one random accesschannel resource of the first BWP. The random access procedure mayfurther comprise transmitting, by the wireless device, the at least onepreamble via the at least one random access channel resource. The atleast one random access channel resource may comprise one or more timeresources and/or one or more frequency resources. In an example, theselected RS may be associated with one of the one or more second RSswith radio quality higher than a second threshold. The second thresholdmay be based on L1-RSRP, or RSRQ, or hypothetical BLER, or SINR.

In an example, the wireless device may stop the first BWP inactivitytimer in response to the transmitting the at least one preamble. In anexample, the wireless device may monitor, for a control information, adownlink control channel in response to the transmitting the at leastone preamble.

In an example, the monitoring the downlink control channel may comprisesearching for the control information in the downlink control channeladdressed for an identifier (e.g. C-RNTI, CS-RNTI) associated with thewireless device.

In an example, the wireless device may complete the random accessprocedure for the beam failure recovery in response to receiving thecontrol information. The wireless device may successfully complete thebeam failure recovery in response to completing the random accessprocedure.

In an example, the wireless device may restart the first BWP inactivitytimer in response to the completing the beam failure recoverysuccessfully.

In an example, the one or more configuration parameters may furtherindicate radio resources of a dedicated coreset. In an example, thecontrol information may be received on the dedicated coreset.

In an example, the one or more configuration parameters may furtherindicate radio resources of a dedicated coreset. In an example, thecontrol information may be received on the dedicated coreset or a commoncoreset.

In an example, the one or more configuration parameters may furtherindicate radio resources of a dedicated coreset. In an example, thecontrol information may be received on a first coreset. The wirelessdevice may be monitoring the first coreset before a random accessprocedure for a beam failure recovery is initiated. In an example, thecontrol information may be received on the first coreset.

In an example embodiment, the at least one PDCCH of the second BWP mayimprove during a random access procedure for a beam failure recovery. Awireless device may monitor the at least one PDCCH before the randomaccess procedure is initiated. In an example, the wireless device maymonitor the at least one PDCCH while the random access procedure isongoing. In an example, while the random access procedure is ongoing, ablockage between a wireless device and a serving cell may not exist. Inan example, a beam failure of the second BWP may be caused by a fadingdip (e.g. deep fading). The fading deep may not exist during the randomaccess procedure.

In an example, a MAC entity of the wireless device may receive a DCI inon the at least one PDCCH during the random access procedure (e.g.before the random access procedure is completed). In an example, the DCImay be for BWP switching of a serving cell. In an example, the wirelessdevice may stop the random access procedure for a beam failure recovery(e.g. ongoing) in response to the receiving the DCI. In an example, thewireless device may switch to a new BWP indicated by the DCI indicatingBWP switching. In an example, the wireless device may be in RRCConnected state after the switching to the new BWP. The wireless devicemay not initiate a random access procedure on the new BWP in response tothe switching to the new BWP.

In legacy systems, the base station may transmit a random-accessresponse (RAR) for a random-access procedure of an SCell on a primarycell (PCell). Based on transmitting RAR, the wireless device may stopthe BWP inactivity timer of the PCell to avoid BWP switching on thePCell. When the SCell is deactivated (e.g., by MAC-CE transmitted by thebase station or an expiry of the SCell deactivation timer) during therandom-access procedure, the wireless device does not continue therandom-access procedure for the deactivated SCell. Implementation oflegacy systems may increase mis-alignment in increased mis-alignmentbetween timers of a base station and wireless device. There is a need toimplement an enhanced BWP inactivity timer to reduce mis-alignmentbetween timers of a base station and wireless device.

In an example embodiment, the wireless device may restart the BWPinactivity timer of the PCell based on (in response to) deactivation ofthe SCell with an ongoing random access procedure. Example embodimentsmay avoid the BWP misalignment between the wireless device and the basestation and/or reduce the gap (misalignment) between the BWP inactivitytimers at the wireless device and the base station from increasing.

FIG. 37 is an example of downlink beam failure recovery procedure for abandwidth part as per an aspect of an embodiment of the presentdisclosure. FIG. 38 is a flow diagram of the downlink beam failurerecovery procedure disclosed in FIG. 37 . A wireless device may receive,from a base station, one or more messages comprising configurationparameters (time T0). The one or more messages may comprise one or moreRRC messages (e.g. RRC connection reconfiguration message, or RRCconnection reestablishment message, or RRC connection setup message). Inan example, the configuration parameters may comprise configurationparameters for a primary cell and one or more secondary cells. The oneor more secondary cells may comprise a first secondary cell. In anexample, the configuration parameters may comprise bandwidth part (BWP)configuration parameters for a plurality of BWPs. The plurality of BWPsmay comprise a first plurality of BWPs of the primary cell comprising afirst DL BWP, a first BWP (e.g. UL BWP) and a second BWP (e.g. DL BWP).The plurality of BWPs may comprise a second plurality of BWPs of thefirst secondary cell comprising a second DL BWP, a third BWP (e.g. ULBWP) and a fourth BWP (e.g. DL BWP).

In an example, a wireless device may be configured with carrieraggregation (CA). A base station may transmit, to the wireless device,an SCell Activation/Deactivation MAC CE activating the first secondarycell. In response to receiving the SCell Activation/Deactivation MAC CE,the wireless device may activate the first secondary cell. In anexample, in response to receiving the SCell Activation/Deactivation MACCE, the wireless device may start or restart a SCell deactivation timerassociated with the first secondary cell (time T1).

In an example, a wireless device may receive a first DCI indicatingswitching a first active BWP of the primary cell from the first DL BWPto the second BWP (time T2). In an example, the first DCI may comprise afirst BWP indicator. The wireless device may determine that the firstDCI indicates BWP switching in response to the first BWP indicatorindicating a BWP different from the first active BWP. The wirelessdevice may start a first inactivity timer in response to switching thefirst active BWP from the first DL BWP to the second BWP (time T2).

In an example, a wireless device may receive a second DCI indicatingswitching a second active BWP of the first secondary cell from thesecond DL BWP to the fourth BWP (time T3). In an example, the second DCImay comprise a second BWP indicator. The wireless device may determinethat the second DCI indicates BWP switching in response to the secondBWP indicator indicating a BWP different from the second active BWP. Thewireless device may start a second inactivity timer in response toswitching the second active BWP from the second DL BWP to the fourth BWP(time T3).

In an example, the wireless device may transmit a random access preamble(time T5) via the third BWP (e.g., active BWP) of the first secondarycell in response to initiating a random access procedure (e.g.contention free random access) for the first secondary cell (time T4).In an example, the random access preamble may be dedicated to thewireless. In an example, the random access preamble may be UE-specificand may be configured for the wireless device by the base station. In anexample, the random access procedure may be for a beam failure recoveryof the fourth BWP of the first secondary cell.

In an example, in response to the initiating the random accessprocedure, the wireless device may stop a first inactivity timer of thesecond BWP of the primary cell and a second inactivity timer of thefourth BWP of the first secondary cell (time T4). The wireless devicemay start a response window (e.g. ra-ResponseWindow) at a first PDCCHoccasion from the end of the transmitting the random access preamble(time T5). In an example, the first PDCCH occasion may be on the secondBWP of the primary cell. The response window may be configured by ahigher layer (e.g. MAC, RRC). The wireless device may monitor the firstPDCCH occasion for a third DCI while the response window is running.

In an example, an SCell deactivation timer of the first secondary cellmay expire while the random access procedure is ongoing (time T6). Inresponse to an expiry of the SCell deactivation timer of the firstsecondary cell while the random access procedure is ongoing, thewireless device may stop the second inactivity timer of the fourth BWP(if running). In an example, in response to an expiry of the SCelldeactivation timer of the first secondary cell while the random accessprocedure is ongoing, the wireless device may restart the firstinactivity timer of the second BWP of the primary cell.

In an example, restarting the first inactivity timer of the second BWPof the primary cell in response to an expiry of the SCell deactivationtimer of the first secondary cell may decrease a power consumption of awireless device.

In an example embodiment, a wireless device may receive one or moremessages comprising configuration parameters. The one or more messagesmay comprise one or more RRC messages. The configuration parameters maycomprise one or more beam failure recovery (BFR) configurationparameters of a serving cell. The one or more BFR configurationparameters may comprise a first set of RS resource configurations. Thefirst set of RS resource configurations may comprise one or more firstRSs (e.g., CSI-RS or SS blocks). The one or more BFR configurationparameters may further comprise a second set of RS resourceconfigurations comprising one or more second RSs (e.g., CSI-RS or SSblocks). The wireless device may measure radio link quality of one ormore beams associated with the one or more first RSs and/or the one ormore second RSs. In an example, the one or more configuration parametersmay further indicate radio resources of a dedicated coreset.

In an example, the wireless device may assess a first radio link qualityof the one or more first RSs against a first threshold. In an example,the first threshold (e.g. hypothetical BLER, L1-RSRP) may be a firstvalue provided by a higher layer (e.g. RRC, MAC). The wireless devicemay monitor at least one PDCCH. At least one RS (e.g., DM-RS) of the atleast one PDCCH may be associated with (e.g., QCLed) the one or morefirst RSs.

A wireless device may detect a beam failure on the serving cell when thefirst radio link quality of the one or more first RSs meets certaincriteria. For example, a beam failure may occur when RSRP/SINR of theone or more first RSs is lower than the first threshold and/or BLER ishigher than the first threshold. The assessment may be for a consecutivenumber of times with a value provided by a higher layer (e.g. RRC, MAC).

In response to detecting the beam failure on the serving cell, thewireless device may initiate a random access procedure for a beamfailure recovery (BFR) procedure of the serving cell. In an example, inresponse to initiating the random access procedure, the wireless devicemay initiate a candidate beam identification procedure if configuredwith the second set of RS resource configurations. In an example, thewireless device may not initiate a candidate beam identificationprocedure if not configured with the BFR configuration parameters (e.g.,contention free random access resources for BFR). In an example, thewireless device may not initiate a candidate beam identificationprocedure if not configured with the second set of RS resourceconfigurations.

For the candidate beam identification procedure, the wireless device mayidentify a first RS in the one or more second RSs. In an example, asecond radio link quality (e.g. BLER, L1-RSRP) of the first RS may bebetter (e.g. lower BLER or higher L1-RSRP or higher SINR) than a secondthreshold. In the example, the second threshold may be a second valueprovided by the higher layer (e.g. RRC, MAC).

In an example, the wireless device may not identify a first RS in theone or more second RSs with a second radio link quality better than asecond threshold. In response to not identifying the first RS, thewireless device may initiate a contention-based random access for a beamfailure recovery.

In an example, in response to detecting the beam failure and notidentifying the first RS, the wireless device may initiate a beamfailure recovery request (BFRQ) transmission. The BFRQ transmission maycomprise transmitting, in a first slot, the at least one preamble viathe at least one PRACH resource for the BFR procedure. In an example,the at least one preamble may not be UE-specific. In an example, the atleast one PRACH resource for the BFR procedure may not be UE-specific(e.g. shared by other users). In response to transmitting the at leastone preamble in the first slot, the wireless device may start, from asecond slot, monitoring for a BFR response. The monitoring for the BFRresponse may comprise monitoring at least one second PDCCH in one ormore dedicated coresets associated for a second DCI (e.g. a downlinkassignment or an uplink grant) within a configured response window. Thesecond DCI may be with CRC scrambled by a C-RNTI of the wireless device.In an example, the one or more dedicated coresets may be configured bythe base station to the wireless device via by the one or moreconfiguration parameters. In an example, the one or more dedicatedcoresets may be used for a random access procedure for a BFR. In anexample, the random access procedure may be contention-free randomaccess or contention-based random access.

In an example, in response to receiving the second DCI on the at leastone second PDCCH in the one or more dedicated coresets, within theconfigured response window, the random access procedure for the BFRprocedure may be successfully completed.

Example embodiments also enhance existing BFR procedures for SCells. Inan example, a wireless device may stop/abort an ongoing BFR procedure ofan SCell in response to an expiry of SCellDeactivationTimer. In anexample, a wireless device may stop and/or reset SCellDeactivationTimerin response to initiating a BFR procedure. The SCellDeactivationTimermay be restarted when the BFR procedure is completed. In an example, awireless device may restart SCellDeactivationTimer, during an ongoingBFR procedure, in response to an expiry of the SCellDeactivationTimer.In an example, a wireless device may not deactivate an SCell in responseto an expiry of SCellDeactivationTimer while a BFR procedure is ongoing.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of base stations or a plurality ofwireless devices in a coverage area that may not comply with thedisclosed methods, for example, because those wireless devices or basestations perform based on older releases of LTE or 5G technology.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 39 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3910, a wireless device may receive one ormore messages comprising configuration parameters. The configurationparameters may indicate: a plurality of bandwidth parts (BWPs)comprising a first BWP and a second BWP; and a timer value for a BWPinactivity timer. At 3930, the BWP inactivity timer associated with thetimer value may be started in response to switching to the first BWP asan active BWP at 3920. At 3940, a beam failure recovery procedure may beinitiated based on reaching a number of beam failure instanceindications for the first BWP. Based on an expiry of the BWP inactivitytimer during the beam failure recovery procedure at 3950, the beamfailure recovery procedure for the first BWP aborted at 3960, and thefirst BWP may be switched to the second BWP as the active BWP at 3970.According to an example embodiment, a random-access procedure may beinitiated at 3980 based on the switching of the first BWP to the secondBWP as the active BWP (at 3970). According to an example embodiment, achannel state information (CSI) report for the second BWP may betransmitted at 3990 based on the switching the first BWP to the secondBWP as the active BWP (at 3970).

According to an example embodiment, the first BWP may be a non-defaultBWP. According to an example embodiment, the second BWP may be a defaultBWP. According to an example embodiment, the configuration parametersmay further indicate a beam failure recovery timer. According to anexample embodiment, the beam failure recovery timer may start based onthe initiating the beam failure recovery procedure. According to anexample embodiment, the beam failure recovery timer may stop based onthe expiry of the BWP inactivity timer. According to an exampleembodiment, the wireless device may stop monitoring at least onedownlink control channel of the first BWP based on the switching thefirst BWP to the second BWP as the active BWP. According to an exampleembodiment, the wireless device may start monitoring at least one seconddownlink control channel of the second BWP based on the switching thefirst BWP to the second BWP as the active BWP. According to an exampleembodiment, the configuration parameters may further indicate one ormore reference signals for the first BWP. According to an exampleembodiment, the one or more reference signals may comprise one or morechannel state information reference signals. According to an exampleembodiment, one or more reference signals may comprise one or moresynchronization signal/physical broadcast channel blocks. According toan example embodiment, the configuration parameters may further indicatethe number of beam failure instance indications for the first BWP.According to an example embodiment, a beam failure instance indicationof the beam failure instance indications may comprise an assessment ofone or more reference signals with radio quality lower than a threshold.According to an example embodiment, the configuration parameters mayfurther indicate the threshold. According to an example embodiment, thethreshold may be based on a hypothetical block error rate. According toan example embodiment, the initiation of the beam failure recoveryprocedure may comprise transmitting an uplink signal for the beamfailure recovery procedure via an uplink resource. According to anexample embodiment, the uplink resource may comprise a physical uplinkcontrol channel resource. According to an example embodiment, the uplinkresource may comprise a physical uplink shared channel resource.

FIG. 40 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. A bandwidth part (BWP) inactivity timer may bestarted at 4020 based on switching to a first BWP at 4010. At 4030, abeam failure recovery procedure may be initiated for the first BWP. At4050, the beam failure recovery procedure may be aborted, based on anexpiry of the BWP inactivity timer during the beam failure recoveryprocedure (4040).

FIG. 41 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4110, a wireless device may receive one ormore messages comprising configuration parameters of a bandwidth part(BWP). The configuration parameters may indicate a timer value for a BWPinactivity timer. At 4130, the BWP inactivity timer associated with thetimer value may be started in response to switching to the BWP as anactive BWP (4120). At 4150, a physical uplink control channel based beamfailure recovery procedure may be initiated based on reaching a numberof beam failure instance indications for the BWP (4140). At 4160, theBWP inactivity timer may be stopped based on the initiating the physicaluplink control channel based beam failure recovery procedure. At 4180,the BWP inactivity timer may be restarted in response to completing thebeam failure recovery procedure (4170).

FIG. 42 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4220, a bandwidth part (BWP) inactivity timermay be started based on switching to a BWP (4110). At 4240, the BWPinactivity timer may be stopped based on initiating a physical uplinkcontrol channel based beam failure recovery procedure for the BWP(4230). At 4260, the BWP inactivity timer may be restarted based oncompleting the physical uplink control channel based beam failurerecovery procedure (4250).

FIG. 43 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4310, a wireless device may receive one ormore messages comprising configuration parameters. The configurationparameters may indicate: a plurality of bandwidth parts (BWPs)comprising a first BWP and a second BWP; and a parameter indicating afirst period of time. At 4320, the first BWP may be switched to as anactive BWP. At 4340, a beam failure recovery procedure may be initiatedbased on reaching a number of beam failure instance indications for thefirst BWP (4330). At 4360, the active BWP may switch from the first BWPto the second BWP during the beam failure recovery procedure based onnot receiving any downlink control information (DCI) for the first BWPduring the first period of time (4350). At 4370, the beam failurerecovery procedure for the first BWP may be aborted based on theswitching.

FIG. 44 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4410, a device may switch to a firstbandwidth part (BWP). At 4420, a beam failure recovery procedure may beinitiated for the first BWP. At 4440, the beam failure recoveryprocedure may be aborted during the beam failure recovery procedure,based on not receiving any downlink control information (DCI) for thefirst BWP during a first period of time (4430).

FIG. 45 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4510, a wireless device may receive one ormore messages comprising configuration parameters. The configurationparameters may indicate a timer value of a bandwidth part (BWP)inactivity timer. At 4530, the BWP inactivity timer associated with thetimer value may be started in response to switching to a first BWP as anactive BWP (4520). At 4550, a random-access procedure for a beam failurerecovery may be initiated based on reaching a number of beam failureinstance indications for at least one downlink control channel of thefirst BWP (4540). At 4560, the BWP inactivity timer may be stopped basedon initiation of the random-access procedure. At 4570, the at least onedownlink control channel may be monitored for control informationaddressed to the wireless device. At 4585, the random-access procedurefor the beam failure recovery may be stopped in response to receivingthe control information via the at least one downlink control channel(4580). At 4590, the BWP inactivity timer may be restarted based on thestopping of the random-access procedure. According to an exampleembodiment, action 4590 may continue at 4620 where a secondrandom-access procedure may not be initiated on the second BWP based onthe random-access procedure being initiated for the beam failurerecovery (4610).

According to an example embodiment, the control information may beaddressed to a configured scheduling radio network temporary identifier(CS-RNTI) of the wireless device. According to an example embodiment,the first BWP may switch to a second BWP based on the controlinformation indicating the second BWP. According to an exampleembodiment, the first BWP may be a non-default BWP. According to anexample embodiment, the configuration parameters may further indicateone or more reference signals for the first BWP. According to an exampleembodiment, the one or more reference signals may comprise one or morechannel state information reference signals. According to an exampleembodiment, the one or more reference signals may comprise one or moresynchronization signal/physical broadcast channel blocks. According toan example embodiment, the configuration parameters may further indicatethe number of first BWP beam failure instance indications. According toan example embodiment, a beam failure instance indication of the firstBWP beam failure instance indications may comprise an assessment of oneor more reference signals with radio quality lower than a threshold.According to an example embodiment, the configuration parameters mayfurther indicate the threshold. According to an example embodiment, thethreshold may be based on a hypothetical block error rate. According toan example embodiment, the restarting of the BWP inactivity timer mayfurther comprise restarting the BWP inactivity timer based on the timervalue. According to an example embodiment, the control information maycomprise an uplink grant or a downlink assignment. According to anexample embodiment, the switching to the first BWP as the active BWP maybe based on receiving a downlink control information indicating thefirst BWP. According to an example embodiment, the initiation of therandom-access procedure may comprise transmitting a preamble via anuplink resource. According to an example embodiment, the uplink resourcemay be a physical random-access channel resource. According to anexample embodiment, the configuration parameters may further indicate adedicated control resource set. According to an example embodiment, thededicated control resource set may be monitored for a second controlinformation for the beam failure recovery. According to an exampleembodiment, completing the random-access procedure for the beam failurerecovery may be based on receiving the second control information in thededicated control resource set.

FIG. 47 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4720, a bandwidth part (BWP) inactivity timermay be started based on switching to a first BWP (4710). At 4740, theBWP inactivity timer may be stopped based on an initiation of a randomaccess procedure for a beam failure recovery for at least one downlinkcontrol channel of the first BWP at 4730. At 4750, the at least onedownlink control channel may be monitored for a control information. At4770, the random-access procedure for the beam failure recovery may bestopped based on receiving the control information (4760). According toan example embodiment, the BWP inactivity timer may be started based onstopping the random-access procedure.

FIG. 48 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4810, a wireless device may receive one ormore messages comprising configuration parameters for a primary cell anda secondary cell. The configuration parameters may indicate: a firsttimer value of a deactivation timer for the secondary cell; and a secondtimer value of a bandwidth part (BWP) inactivity timer for the primarycell. At 4830, the deactivation timer associated with the first timervalue may be started in response to activating the secondary cell(4820). At 4850, the BWP inactivity timer associated with the secondtimer value may be started in response to switching to a BWP as anactive BWP of the primary cell (4830). At 4860, a random-accessprocedure may be initiated for the secondary cell. At 4870, the BWPinactivity timer may be stopped based on the initiation of therandom-access procedure. At 4885, a determination may be made that thedeactivation timer expired during the random-access procedure. At 4890,the BWP inactivity timer may be restarted in response to thedetermination.

FIG. 49 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4920, a deactivation timer may be startedbased on activating a secondary cell (4910). At 4940, a bandwidth part(BWP) inactivity timer of a primary cell may be started based onswitching to a BWP of the primary cell (4930). At 4960, the BWPinactivity timer may be stopped based on initiating a random-accessprocedure for the secondary cell (4950). At 4980, the BWP inactivitytimer may be restarted based on the deactivation timer expiring duringthe random-access procedure (4970).

FIG. 50 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5010, a secondary cell may be activated. At5030, a bandwidth part (BWP) inactivity timer of a primary cell may bestarted based on switching to a BWP of the primary cell (5020). At 5050,the BWP inactivity timer may be stopped based on initiation of arandom-access procedure for the secondary cell (5040). At 5070, the BWPinactivity timer may be restarted during the random-access procedurebased on not receiving any downlink control information for thesecondary cell (5060).

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1},{cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (i.e.hardware with a biological element) or a combination thereof, all ofwhich may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device. Theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, one or more messages comprising configuration parameters for aprimary cell and a secondary cell, wherein the configuration parametersindicate: a deactivation timer for the secondary cell; and a bandwidthpart (BWP) inactivity timer for the primary cell; starting thedeactivation timer in response to activating the secondary cell;starting the BWP inactivity timer in response to switching an active BWPof the primary cell; stopping the BWP inactivity timer of the primarycell based on initiating a random-access procedure for the secondarycell; and in response to the deactivation timer of the secondary cellexpiring during the random-access procedure, restarting the BWPinactivity timer of the primary cell.
 2. The method of claim 1, whereinthe random-access procedure is for a beam failure recovery of thesecondary cell.
 3. The method of claim 1, wherein the activating thesecondary cell comprises receiving a medium access control controlelement (MAC CE) indicating activation of the secondary cell.
 4. Themethod of claim 1, further comprising initiating the random accessprocedure for the secondary cell.
 5. The method of claim 1, furthercomprising determining that the deactivation timer of the secondary cellexpires during the random access procedure.
 6. The method of claim 1,wherein the switching the active BWP comprises switching to a first BWPof the primary cell as the active BWP.
 7. The method of claim 6, whereinthe first BWP is a non-default BWP.
 8. The method of claim 1, whereinthe switching the active BWP is further in response to receiving adownlink control information (DCI) indicating a first BWP to switch toas the active BWP.
 9. The method of claim 1, wherein the deactivationtimer is started with a first timer value.
 10. The method of claim 1,wherein the BWP inactivity timer is started with a second timer value.11. A wireless device comprising: one or more processors; memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: receive one or more messages comprisingconfiguration parameters for a primary cell and a secondary cell,wherein the configuration parameters indicate: a deactivation timer forthe secondary cell; and a bandwidth part (BWP) inactivity timer for theprimary cell; start the deactivation timer in response to activating thesecondary cell; start the BWP inactivity timer in response to switchingan active BWP of the primary cell; stop the BWP inactivity timer of theprimary cell based on initiating a random-access procedure for thesecondary cell; and in response to the deactivation timer of thesecondary cell expiring during the random-access procedure, restart theBWP inactivity timer of the primary cell.
 12. The wireless device ofclaim 11, wherein the random-access procedure is for a beam failurerecovery of the secondary cell.
 13. The wireless device of claim 11,wherein the activating the secondary cell comprises receiving a mediumaccess control control element (MAC CE) indicating activation of thesecondary cell.
 14. The wireless device of claim 11, wherein theinstructions further cause the wireless device to initiate the randomaccess procedure for the secondary cell.
 15. The wireless device ofclaim 11, wherein the instructions further cause the wireless device todetermine that the deactivation timer of the secondary cell expiresduring the random access procedure.
 16. The wireless device of claim 11,wherein the switching the active BWP comprises switching to a first BWPof the primary cell as the active BWP.
 17. The wireless device of claim16, wherein the first BWP is a non-default BWP.
 18. The wireless deviceof claim 11, wherein the switching the active BWP is further in responseto receiving a downlink control information (DCI) indicating a first BWPto switch to as the active BWP.
 19. The wireless device of claim 11,wherein: the deactivation timer is started with a first timer value; andthe BWP inactivity timer is started with a second timer value.
 20. Asystem comprising: a base station comprising one or more firstprocessors and memory storing instructions that, when executed by theone or more first processors, cause the base station to: transmit one ormore messages comprising configuration parameters for a primary cell anda secondary cell, wherein the configuration parameters indicate: adeactivation timer for the secondary cell; and a bandwidth part (BWP)inactivity timer for the primary cell; a wireless device comprising oneor more second processors and memory storing instructions that, whenexecuted by the one or more second processors, cause the wireless deviceto: receive, from the base station, the one or more messages comprisingthe configuration parameters for the primary cell and the secondarycell; start the deactivation timer in response to activating thesecondary cell; start the BWP inactivity timer in response to switchingan active BWP of the primary cell; stop the BWP inactivity timer of theprimary cell based on initiating a random-access procedure for thesecondary cell; and in response to the deactivation timer of thesecondary cell expiring during the random-access procedure, restart theBWP inactivity timer of the primary cell.